Which connector?: Oracle Fusion Field Service

Additional details:

We are seeing late-arriving records in the Activity table that can be missed by the current incremental sync behavior.

Fivetran Support confirmed that the connector queries the Oracle Fusion /activities endpoint using the activity date, and that there is currently no lookback window configured for this table.

In one example, a record had:

• date: 2026-08-08
• timeOfBooking: 2026-08-09 01:07:19

The August 8 sync had already completed before the record became available from the source API. Because subsequent syncs did not query August 8 again, the record was not picked up and required a historical re-sync.

We are requesting a configurable lookback window for the Activity table / /activities endpoint so that each incremental sync can re-query a configurable number of previous days, such as 1–3 days.

This would allow late-arriving records to be captured automatically while preserving normal upsert/deduplication behavior.

Without a lookback window, late-arriving records can remain permanently missing unless we detect them and manually initiate a historical re-sync. This creates a data completeness risk for downstream reporting and operational workflows.

Desired behavior:
Allow customers to configure a lookback period for the Oracle Fusion Activities sync so records that become available after their activity date has already been processed can still be captured automatically.

Related Support Ticket: #405303