Coverage and limitations

Run statuses and budgets

• Completed: supported declared relationships in the selected scope were processed. Findings may still be present.
• Partial: a limit, omission or invalid candidate prevents complete coverage.
• Cancelled: the unfinished snapshot is discarded. Do not use it to make a decision; run the review again.
• NoApplicableData: there were no rows to inspect.
• Failed: the request could not run, or a source changed during collection. Failed results discard inconsistent findings and cannot be exported; run a new review after editing or reimporting.

The default budget is 10,000 source rows and 10,000 relationships; profiles can set 1–100,000. Destination indexes are capped at 100,000 keys per table. The panel accepts CSV files up to 16 MiB, profiles up to 1 MiB, and at most 1,000 selected tables/rules.

The evaluator also enforces hard capture limits: 8 nested levels, 256 fields per row, 2,048 collection elements, 65,536 characters per String value, 200,000 captured value slots and 200,000 destination keys across a snapshot. Snapshot capture and each game-rule report have a 32 MiB budget; game-rule evaluation has a 1,000,000-operation budget. Row keys must fit Unreal’s name limit of 1,023 characters. Exceeding a limit yields an omission, unavailable value or Partial/Not evaluable result; it never becomes a passing result.

Collection uses game-thread batches. Reviews above 256 captured rows evaluate a pure snapshot on a worker; asset loading and export still use the editor thread. Cancellation takes effect between batches and discards unfinished work. No whole-project coverage or guaranteed response time is claimed.

Unsupported relationships

Top-level row-handle fields and arrays or sets of row handles are inspected. Nested references, maps, static arrays and unsupported containers are not inferred. RowTether does not infer arbitrary Name fields or analyze every Blueprint graph. Omissions are reported so a partial review cannot be mistaken for a whole-project check.