Chartbreaker
    Preparing search index...

    Type Alias TradeWarningReason

    TradeWarningReason:
        | "executionsWithoutTimestamp"
        | "inconsistentOrderHistory"
        | "positionNotFullyExplained"
        | "missingEodPrice"
        | "missingFxRate"
        | "unknownBuyPrice"
        | "realizedPnlUnavailable"

    Why a trade summary or a portfolio value history could not be computed completely. A client should switch on this instead of parsing TradeWarning.text, which is free text and may change at any time.

    • executionsWithoutTimestamp: the order executions carry no execution time, so they could not be placed on a timeline and have been ignored altogether.
    • inconsistentOrderHistory: the executions of one security contradict each other or the reported holding (more sold than ever bought, a quantity that goes negative). Nothing could be reconstructed from them, so the security is left out of the value history and its trades are not reported.
    • positionNotFullyExplained: the order archive only covers part of a position, which is typical for brokers that return just the most recent weeks. What is held today is known, but its history reaches further back than the executions do.
    • missingEodPrice: no closing price was available for the security on some days; it has been valued with the last price known before them.
    • missingFxRate: no exchange rate to the portfolio currency exists for the security's currency, so its amounts have not been converted and the totals they enter are off by the conversion.
    • unknownBuyPrice: no buy price could be determined for a position, so it is missing from the buy value (and from the profit it implies).
    • realizedPnlUnavailable: the completed trades could not be computed at all, which leaves the realized profit/loss empty instead of wrong.

    This list may grow, so a client should not assume that it knows every reason.