Known limitations
Current Technical Preview limits
Read these limits before using the preview’s reports.
- The current HTML report is organized around order timelines. Full interaction is desktop-oriented.
- FIX, anomaly, venue-format, asset-class, and input coverage is incomplete.
- Packed JSON can change during the Technical Preview. Do not rely on it as a stable interface for automation.
- The free preview accepts explicit files and produces HTML and optional packed JSON. It limits the details shown and redacts report data.
- Directory and recursive report input are not part of this Free preview.
- v0.1.0a3 does not provide SQLite
.fxtcaseoutput, viewer or inspect commands, hosted uploads, AI explanations, enterprise or compliance readiness, production readiness, or general availability. - Keep report input at or below 5,000,000 bytes. Larger input triggers a warning; above 10,000,000 bytes, reports are refused by default.
- Extraction uses exact identifiers and does not expand relationships. A narrow extract can omit order context. See the trial guide for input requirements and limits.
Check each finding against the source FIX messages. Follow your organization’s procedures before you make a material decision.
v0.1.0a3 support matrix
This describes the published v0.1.0a3 Free Technical Preview. Parser acceptance does not mean complete FIX or venue support.
| Input | Coverage |
|---|---|
| FIX versions | Order scenarios are tested with FIX 4.2 and 4.4. FIX 5.0 and FIXT 1.1 have header-recognition tests only. Generic numeric FIX/FIXT headers can be recognized; that is not version certification. Application-version negotiation is not implemented. |
| Order messages | D (New Order Single), F (Cancel Request), G (Cancel/Replace Request), 8 (Execution Report), 9 (Cancel Reject), and H (Order Status Request) are routed for order analysis. Business Message Reject (j) is routed with an order identifier. Event and anomaly coverage is partial. |
| Session and other messages | A, 0, 1, 2, 3, 4, and 5 are routed as session traffic. Other message types go to Other Traffic. Order messages without identifying tags go to Incomplete Orders. Routing does not imply full analysis or full detail in Free. |
| Report formats | Explicit local text files with SOH, literal ^A, pipe, or whitespace delimiters. Prefixes, wrapped messages, and multiple messages on a line have parser tests. Invalid UTF-8 is replaced during decoding; parsing is not a byte-preserving archive. Directory and recursive input are unavailable in Free. |
| Extraction format | One complete message per physical line, with a consistent SOH, literal ^A, pipe, or single ASCII whitespace delimiter. Requires BeginString, BodyLength, MsgType, and a final CheckSum field with its trailing delimiter. Wrapped messages and suffixes after CheckSum are unsupported. Extraction checks framing, not the numerical correctness of BodyLength or CheckSum. |
| Limit | Behavior |
|---|---|
| Report ordering and dates | Use single-day order input. Multiple explicit files must be chronological and non-overlapping. Unsupported ordering and cross-day order input are refused; overnight/GTC reconstruction is unavailable. |
| Report input size | Up to 5,000,000 bytes total across distinct resolved input files: normal operation. Above 5,000,000 and up to 10,000,000 bytes: warning. Above 10,000,000 bytes: refused by default with exit code 2. An explicit --force-large-input bypasses the refusal with a warning; it does not guarantee memory use or runtime. Temporary snapshots also need space for the consumed input. |
| Extraction selectors | Exact --clordid matches ClOrdID or OrigClOrdID; --orderid matches OrderID; --execid matches ExecID. Repeatable selectors use OR. There is no relationship expansion. A narrow extract can omit context. |
| Extraction caps | One input file; at most 1,048,576 bytes per physical line excluding CR/LF, and 10,000 matching messages. Oversized or malformed lines are skipped. A 10,001st match fails without replacing existing output. No matches exits with code 1 and preserves existing output. The message cap does not enforce report byte limits. |
| Output | What is shown |
|---|---|
| Affected orders | Up to four preview events per affected timeline and broad finding categories. There is no total affected-order or finding-card count cap. |
| Clean orders | Up to five clean-order summaries. Clean orders have no full event timeline in Free; a clean-only report contains summaries. |
| HTML and packed JSON | Both use the Free redacted payload. Raw FIX, exact rule details, original event/message evidence references, and ExecID values are removed. Order identifiers, symbols, prices, quantities, timestamps, and source labels can remain. Redaction does not guarantee anonymity. Protect both outputs as sensitive. |
| Known interaction limitation | During initial report rendering, a rerender can remove keyboard focus and Enter may fail to activate a View event link. Frequency and mouse effects have not been established. This is deferred for a later release. |
| Unavailable features | Trade bust/correct reconstruction is incomplete. A cancel reject with an unseen OrigClOrdID has no dedicated unknown-reference finding. Packed JSON can change; do not depend on its format for automation. This release has no public Pro offer. |