Run a sync now, or change how often it runs
Click Sync on the tool's card and keep the tab open. There is no setting for how often the scheduled refresh runs — it follows whether anyone has signed in recently, and this article explains what that means for your data. If a sync has been running for hours, read A sync is stuck, or never finishes instead.
Run a sync now
Open Connected Tools.
The page is headed Integrations. You can also start a sync from Data sources, under Intelligence Studio, or from the tool's own page. All three start the same run.
Click Sync on the tool's card.
On the tool's own page the button reads Sync now instead.
Leave the tab open until the status line says it has finished.
The chunk loop runs in your browser, which is why the line reads "keep this tab open". Close it and the run stops where it is. Nothing is lost: the cursor is saved, so the next sync carries on from there.
Read the result line.
A first load counts up against your tool's own total with a time estimate, then finishes with "Fully synced — N records". A later run says "Up to date — N changes since your last sync", or "Up to date — no changes since your last sync".
Note
Connecting a tool starts its first sync on its own. You do not need to press anything after a successful connect.
How often the scheduled refresh runs
There is no setting for this, in the workspace or on the tool. The schedule follows the people using the workspace, because every sync wakes that workspace's database and an idle account should not be woken twenty-four times a day for data nobody is reading.
| Your workspace | How often each connected tool is refreshed |
|---|---|
| Somebody signed in within the last seven days | Every hour |
| Nobody has signed in for seven days | About every six hours — four times a day |
| A first load is still running, or a walk was cut short | Four times an hour, until it finishes |
The moment somebody signs in, the workspace counts as active again and the next hourly run picks it up.
The scheduled job fires on the hour and again at quarter past, half past and quarter to. The hourly run refreshes everything that is due. The three in between only advance work already in motion — a first load, or a walk that ran out of time — which is what makes a large first load land in hours rather than taking most of a day.
Tip
A manual sync is never slowed down by any of this. If you have changed something in your CRM and want to see it now, press Sync.
What an incremental sync re-reads
A first run is a backfill: it walks your whole store, page by page, with a resume token, so it is exhaustive and picks up again after an interruption. Every run after that is incremental: MarqIQ asks your tool which records changed since the coverage it last claimed, and reads only those.
Each chunk writes by upsert, so running the same chunk twice changes nothing. That is why an interrupted run costs you nothing and why Sync is safe to press whenever you are unsure.
Why two syncs never run at once
One run per tool per workspace holds a lease for two minutes at a time, renewed while it works. A second run that arrives finds the lease taken and stops quietly with "Another sync is already running for this workspace — it will finish on its own."
That message is shown in green, not red. It means the scheduled run has your workspace and your data is being refreshed right now. There is nothing to do.
Reading the last run
Each run records more than one number. The Connected Data Sources card on Attribution & Journeys shows the parts you can act on.
| What it says | What it means |
|---|---|
| N contacts | People MarqIQ holds from that tool. |
| Not synced | This tool is connected but holds no records yet. |
| Last sync: a date | When the last run finished. It is not the same as how far the data is covered. |
| A line in red | Something went wrong, in your tool's own words. This line is only ever a failure. |
| A line in grey | Narration, not a failure: lane results, coverage warnings, "more to sync". It is shown only when there is no red line. |
| Covered through Nh ago | In amber. How far behind the coverage is. It appears only once that is more than 24 hours, and it is not a failure. |
A run that set records aside is recorded as partial rather than successful, even when nothing threw.
Note
A run also records how many records it fetched against how many it wrote. A gap between the two means records arrived from your tool and did not land. No screen shows that pair today, so ask support to read it from the run if a count looks short.
Note
A run that sets records aside does not stop. The bad record is kept with its reason, the rest of the batch continues, and the count appears as records failed on that run.
Deleted records, and the weekly count check
A delta walk can only ask what changed since a moment in time. It cannot notice a record that was merged, or an association that moved without changing a timestamp. So once a week, per source, MarqIQ asks your tool how many records it holds and compares that with its own copy.
The comparison is a check, not a repair. It never deletes, never marks a record gone and never starts a re-walk on its own, because a count mismatch has innocent explanations — a walk still in flight, records the credential cannot see, a filter difference. Drift is reported so you can decide.
If it did not work
The sync stops part-way with an error and the words "progress is saved"
Why: A chunk came back with an error after MarqIQ had already retried it. The cursor and everything written so far are kept.
Fix: Read the message — it is your tool's own words — fix the cause, then click Sync again. The run resumes rather than restarting.
You closed the tab and the count stopped moving
Why: A manual run is driven by your browser. Closing the tab ends the loop.
Fix: Open the tool again and click Sync. It carries on from the saved cursor. The scheduled run would have picked it up as well.
The very first sync says the workspace's database is not ready
Why: Each workspace gets its own database, created on first use, which takes about twenty seconds. MarqIQ waits and retries four times on its own before it gives up.
Fix: Wait a few minutes and click Sync.
A connected tool has no Sync button, and the card reads "Mapping only · no record sync yet"
Why: Only eleven connectors have a sync engine. The rest connect so you can map fields, and MarqIQ does not pull their records.
Fix: Nothing to fix. Use that tool for field mapping, and connect one of the eleven if you want its records analysed.
Your last-synced date is a day old although nothing is broken
Why: Nobody has signed in to this workspace for seven days, so it is refreshed about four times a day instead of hourly.
Fix: Sign in. The workspace counts as active again and the next hourly run refreshes it. Or click Sync and have it now.
The number of records in MarqIQ does not match your CRM
Why: The weekly count check reports drift and deliberately never repairs it, so a difference can sit there until you act on it.
Fix: Read the grey notes line on that tool's card. It names the drift both ways — "are in the source but not here", which a full resync fixes, or "are here but not in the source", which means records were deleted in your tool without appearing in its deletes feed.
Next steps
Related articles
Was this article helpful?