Schedules and Run History
Overview
Each sync runs on its own schedule, keeps a history window for its first run, and produces a record every time it runs. This page covers scheduling, running a sync on demand, stopping one mid-run, and reading what a run actually did.
Scheduling
In the sync editor, choose Hourly or Daily under Schedule. On the first run, the sync looks back over the History window (days) you set (up to 730 days) to bring in past activity; after that, each run only pulls what's new since the last one.
If you ever change a sync's query or settings and want it to reload its full history rather than continue forward from where it left off, open the sync and check Re-sync history from the start before saving.
The safe-overlap and message_id story
Behind the scenes, every run has a small overlap with the previous one — configurable under Advanced settings as Overlap window (minutes) — so nothing falls through the cracks if a row shows up in your warehouse a little late. Combined with message_id, this overlap is always safe: re-checking the same period twice never creates duplicates, because a row with a message_id TrailSpark has already seen is simply recognized and skipped.
History window vs. your retention period
The History window (days) field controls how far back the first sync looks. Your TrailSpark plan also has an event retention period — how long TrailSpark keeps event history before it ages out.
If you set a history window longer than your plan's retention (for example, bringing in 90 days of history on a plan with 30-day retention), the older imported rows are cleaned up again shortly after they're imported, since they're already past their retention age. TrailSpark shows a warning in the sync's run history when this happens. If you want that older history to stick around, either shorten the history window to match your retention, or talk to your TrailSpark contact about a longer-retention plan.
Running on demand
Click Run now next to any sync for an on-demand run outside its schedule. This is useful right after you've fixed a query, or whenever you don't want to wait for the next scheduled run.
Stopping a sync
If you notice a sync running with the wrong query or settings, you don't have to wait for it to finish. Click Stop — next to it in the syncs list, or on the running row in its History — and confirm Stop this sync?. The sync stops within a few seconds. Rows it already imported stay, and nothing is lost or duplicated: the next sync (scheduled or Run now) simply re-reads the same period.
Once stopped, fix your query or settings, then click Run now to redo it properly.
Reading run history
Click History on any sync to see its recent runs. Each row shows:
| Column | What it shows |
|---|---|
| Started | When the run began |
| Duration | How long it ran |
| Rows synced | How many rows were successfully sent |
| Duplicates | Rows recognized as already synced (by message_id) and skipped |
| Rejected | Rows this feed couldn't accept — expand the run to see the reason for each one |
| Status | Syncing, Synced, Partial, Stopped, Failed, or Not yet synced |
Click a run with something to show, and it expands to list rejected rows with a plain-language reason for each one — things like "Missing event time," "No user identifier," or "Event time too old or in the future." Fix the underlying data or query and the next run picks up the corrected rows.
Before you ever save a sync, its Preview shows an estimate of how much data the query will scan per run — see Designing Sync Queries. Each sync also has a Scan limit per run (GB) under Advanced settings; if a run would need to scan more than that limit, it fails with a message telling you so rather than running an unexpectedly large query.
Reconnecting a Google account
If a connection was made with Sign in with Google and it stops working — access was revoked, the grant expired, or a Google Workspace admin changed something — you'll see a Reconnect your Google account notice on the connection, and any syncs using it show a note that they need you to reconnect. Click Reconnect your Google account and sign in again; nothing else about your syncs needs to change.
Next Steps
- Designing Sync Queries — fix a query that's producing rejected rows
- Connecting BigQuery — connection options and IAM roles
- BigQuery Connector Overview — how this connector fits with everything else