Sync Scheduling

Querri answers from a copy of your connected data, and that copy is only as fresh as its last sync. A schedule refreshes it for you.

Two kinds of sync

Full Refresh

A full refresh reloads everything the connector syncs. It works for every connector. Use it:

• to pick up rows deleted at the source, which an incremental sync can’t see
• for tables with no column that tracks changes
• for apps that don’t support incremental sync
• as a regular clean baseline alongside incremental syncs

Incremental

An incremental sync fetches only the records that changed since the last successful run. It tracks them with a cursor: a column, such as updated_at, that changes whenever a row does. After the first load, it’s much faster than a full refresh on large tables.

• It works on database tables that have the cursor column, and on Salesforce and NetSuite. For other apps, use Full Refresh.
• It can’t see rows deleted at the source.
• For database tables, only tables that have the cursor column sync incrementally. The others are skipped.

Using both

A connector can have one schedule of each kind. For a connector that supports incremental sync, a common pattern:

Schedule	Repeat	Why
Incremental	Every Hour	Picks up new and changed records quickly
Full Refresh	Every Day or Every Week	Catches deleted rows and anything the cursor missed

Setting up a schedule

Only the connector’s owner can manage its schedules. Anyone else sees Owner Access Required and “Only the connector owner can manage schedules.”

1. Open the connector. Admins can click the configure icon on its card in Settings → Connectors. In the Library, right-click the connector in the Connectors section and choose Configure…, then open its Schedule section.

2. Go to Schedule, and choose Full Refresh or Incremental. The tab appears once the connector exists.

3. Set Start Date and Time. They default to tomorrow at 06:00. For an incremental schedule, they only show when it repeats Every Hour.

4. Choose how often under Repeat:

   Kind	Options	Default
   Full Refresh	Every Day, Every Week, Every Month	Every Day
   Incremental	Every Hour, Every Day, Every Week	Every Hour

   Weekly schedules run on Mondays, and monthly ones on the 1st.

5. Incremental only: under Cursor Configuration, enter a Cursor Field, or leave it blank to auto-detect (see Choosing a cursor field).

6. Full Refresh only: decide whether to tick Skip sources with active incremental sync (see below).

7. Leave Enable schedule immediately ticked to start the schedule now. Untick it to create the schedule paused.

8. Click Create Schedule.

Times use your browser’s time zone.

After Save and Load Data, the progress card offers a shortcut: Sync daily creates a daily full refresh at 06:00.

Skip sources with active incremental sync

This option on a full refresh leaves out tables that an incremental schedule already keeps up to date: “Large tables already synced incrementally will be skipped. You can always sync them manually from the Library.”

It saves time on big tables. The trade-off is that deleted rows in those tables aren’t cleared by the full refresh, so sync them by hand now and then.

Choosing a cursor field

The Cursor Field matters for database tables: PostgreSQL, MySQL, SQL Server, Redshift and BigQuery. Pick a column that changes whenever a row is added or edited:

Column	Good for	Catches
updated_at / modified_at	Tables that record edits	New and changed rows (best choice)
created_at	Append-only tables	New rows only
An auto-incrementing id	Append-only tables	New rows only

Tables without that column are skipped by the incremental schedule. Leave them to the full refresh.

Sign-in and key-based apps don’t read this box. Salesforce and NetSuite track changes with their own last-modified field, so leave Cursor Field blank for them.

Not every table suits incremental sync

Use a full refresh for:

• Lookup and reference tables that rarely change and have no timestamp column
• Tables loaded by truncate-and-reload jobs, where every row looks new after each reload

Rules and limits

• One of each kind. A connector has at most one full refresh schedule and one incremental schedule. To change one, edit it and click Update Schedule.

• Minimum gaps. Querri enforces a minimum time between runs. The Repeat options all fit within these.

  Schedule	Minimum gap
  Incremental	15 minutes
  Full Refresh, with a cursor	1 hour
  Full Refresh, without a cursor	24 hours
  Any QuickBooks Online schedule	1 hour

• Plan limit. Schedules count toward your plan’s connector limit. When you reach it, creating a schedule fails with “Connector limit reached for current plan. Upgrade to add more.”

• Credits. Each scheduled sync uses credits when it runs: 1 credit per sync at the default rates, and your plan may differ. Syncs you start by hand don’t use credits. See Credits.

Managing a schedule

When a schedule exists, its sub-tab shows it above the form:

• Schedule Active or Schedule Paused
• Schedule: a plain description, such as how often it runs
• Next Run: in your local time
• Last Run: a status and a time

The switch pauses or resumes the schedule as soon as you click it. The trash icon deletes it, after you confirm. To change the schedule, edit the form and click Update Schedule.

After three failed runs in a row, Querri turns the schedule off and says “Schedule auto-disabled after {n} consecutive failures.” Fix the underlying problem, such as an expired sign-in or a changed password, then switch the schedule back on.

Run history

Below the form is a list of recent sync runs, scheduled and manual, grouped by sync. It refreshes every 15 seconds. Until something has run, it says “No sync runs yet”.

Syncing by hand

You don’t need a schedule to refresh data:

Where	What it runs
Save and Load Data in a database connector’s dialog	A full sync of the selected tables
Load data now, in a connector’s Library view while nothing has loaded yet	A full sync (owner only)
Re-sync now, from a connector’s right-click menu in the Library	An incremental sync for Salesforce and NetSuite, and for a database or BigQuery connector with an Incremental schedule’s cursor field. Connectors that don’t track changes reload everything

To find Load data now, click the connector under Connectors in the Library’s browse panel. It shows when the connector “is connected, but no data has loaded yet”.

Syncs you start by hand don’t use credits.

Troubleshooting

A schedule isn’t running

• If it says Schedule Paused, switch it on.
• If it was auto-disabled after failures, fix the cause, then switch it on.
• If the connector’s sign-in has expired, click Reauthenticate on its Configuration tab first.
• Next Run is in your local time, so check it against your clock, not the source system’s.

The schedule controls are locked

Only the connector’s owner can manage schedules. Ask the owner to set one up.

”Connector limit reached for current plan”

Schedules count toward your plan’s connector limit. Delete a schedule you don’t need, or upgrade.

An incremental sync skipped some tables

Tables that don’t have the cursor column are skipped. Name a column those tables share, or leave them to the full refresh.

Changes are missing after incremental syncs

The cursor column may not change on every kind of edit. Run a full sync (Save and Load Data, or wait for the full refresh). If it keeps happening, choose a better cursor column or rely on full refreshes for that table.

Deleted rows still appear

Incremental syncs can’t see deletions. They clear on the next full refresh, unless that table is skipped by Skip sources with active incremental sync.

Best practices

1. Load everything first. Start with a full load, then add an incremental schedule if the connector supports one.
2. Keep a full refresh. It catches deletions and anything the cursor misses.
3. Prefer timestamps over IDs for database cursors. A timestamp catches edits; an ID only catches new rows.
4. Don’t over-sync. Every scheduled run uses credits, and hourly is usually plenty.
5. Check the run history now and then for failures and skipped tables.

Next Steps

• Data Connectors Overview: all available connectors
• Managing Connections: change, refresh and remove connectors
• Salesforce and NetSuite: apps with incremental sync
• Database Best Practices: prepare tables for syncing
• Credits: what scheduled syncs cost