Qoblex inbound sync
Qoblex inbound sync
Open Settings → Integrations → Qoblex → Manage. The dialog shows the
account, counts, sales date span and last sync. Connecting starts the first
read automatically; you do not need to keep the dialog open.
First catch-up
Twelfth reads every product and reaches back 365 days for sale orders. Reads
are paced to 30 API calls per minute per key, so a large account takes several
minutes or longer. A pass that uses its call budget resumes in the background.
Catching up means that work is still running. Product and sales counts
update as progress is announced. A quiet count alone does not prove the sync
failed; check the status and last error.
Normal refresh schedules
| Source | Schedule |
|---|---|
| Sale orders | New and changed orders every 15 minutes. |
| Catalogue and stock | Full catalogue and location stock pass every hour. |
| Purchase orders | Daily. |
Qoblex is polled; there is no webhook for you to configure. The catalogue is
read in full because this connector cannot reliably ask only for changed
products. Sale-order updates include cancellations, deletions and orders that
revert to quotes.
Sync now
Sync now starts a short pass immediately and reports products and orders
read. If more work remains, the background sync continues. Use it to check a
new connection or an apparent delay; repeatedly pressing it does not make the
account’s API limit disappear.
The dialog shows the account name and currency, products and sales lines
received, the sales date span, the last full catalogue read, and the last sync
or error. Catalogue and sales are separate passes: one recent timestamp does
not prove every pass has completed.
If updates stop
- Catching up: let the pass continue and watch for progress or an error.
- Last sync failed: read the message. A revoked key or missing API access
usually needs reconnection, not another manual sync. - Sync now reads rows: the connection is reachable. Check
data mapping if the expected
figures still do not appear. - Repeated errors or a stalled catch-up: contact Twelfth with the account name
and error shown, without sending your API key.