Why Aren't My TestRail Run Records Updated?
Question
My TestRail RUN records are successfully created and synced to my destination, but fields like passed_count, failed_count, and similar columns don’t update afterward. Why aren’t these changes reflected after the initial sync?
Environment
- Connector: TestRail
Answer
The Fivetran TestRail connector relies on the created_on timestamp when ingesting data from the Run endpoint. The sync cursor only considers newly created records, not updates to existing ones. If a record is updated after the sync cursor moves past its created_on timestamp, those changes may not be captured by incremental syncs.
To address this, we have enabled a weekly override re-sync for the RUN entity. This means:
- All records in the
RUNtable are re-imported once per week on the weekend. - Any updates that may have been missed due to cursor movement are detected and included in the next scheduled re-sync.
- For example, if a record was updated on October 30, 2025, but missed by the incremental sync, those updates are picked up during the next weekend re-sync and delivered to your destination automatically.
- No manual action is required. If you do not see updated values immediately, please wait for the next scheduled weekly re-import.