The REPORT table within Checkr contains background check statuses. Unfortunately the REPORT endpoint doesn't support any parameters or filters other than report_id, which means that Checkr can't fetch updated records directly based on changes in the REPORT endpoint. Due to this limitation, Checkr re-imports the CANDIDATE table once a week to capture updates and deletes, and re-imports the REPORT table at that time.

It would make sense to schedule this particular re-import to occur on a daily basis rather than a weekly basis on Fivetran's end. The rationale is that most background checks will be pending when they're initiated but will typically move to another status within 1-2 days. Customers like us will rely on this field to monitor which background checks aren't clear, and increased data freshness will help reduce the # of false positives we manually check.

tl;dr - Increasing the 'Sync Frequency' of the Checkr connector isn't a good way to increase data freshness, and we'd therefore recommend allowing customers to either configure how often a full sync occurs, or schedule a full sync on the Fivetran side once a day for this particular connector.