Running the integration day to day
Once live, the connector runs by itself every few minutes. A few minutes of checking each day keeps it that way.
| Check | How often | Where |
|---|---|---|
| Is the service running and syncing? | Daily | Connect dashboard › Overview: state and recent cycles. |
| Anything failed or needing attention? | Daily | Transactions and the Events log. |
| Records held until their invoice arrives | No action | They go after the invoice. |
| Daily API limit reached | No action | Sending pauses and continues the next day. |
| Backup of the data folder | Before every upgrade, and regularly | Copy it while the service is stopped, and keep a copy off the server. |
When a record fails
A record the accounting software rejects is marked failed with the reason and is not retried by itself, so one bad record never blocks the rest. Fix the cause, for example create the missing tax in the books, then press Retry failed rows. Network drops are retried automatically.
Keep the sign in healthy
- The connector signs in as its own integration user. Never use a person's login; leave, password changes or exits would stop the sync.
- When the integration licence ends, the connector stops within two minutes. Renew it in time.
- The dashboard only opens on the server itself and its data folder holds secrets. Never share screenshots that show them.
Related guides: Failed and held records · Reading the events log · Backup and upgrade · Security rules.
Still stuck?
Message our support team on WhatsApp in English, Tamil, Malayalam or Hindi.