Sync and data freshness

How TaktSignal stays up to date

• Background sync: the TaktSignal background process reads changes from ERPNext every 15 minutes by default. In the app, Integrations → ERPNext → Auto-sync every changes the interval (5–60 minutes).
• Sync now: Integrations → ERPNext → Sync now reads immediately.
• Incremental: after the first read, only documents changed since the last read are fetched (by modification time), plus a check for documents that disappeared.
• Recalculation: alerts are recalculated after every data change and every few minutes, so time-based alerts (late start, WIP aging) move on even without new data.

Background sync runs while TaktSignal is running — it starts at login by default. If your computer is off, nothing is read; the next start catches up.

Freshness

The dashboard shows the age of each kind of data (inventory, production, customer orders, items & BOMs): the time since it was last read completely. A kind of data that is behind, failed or degraded is flagged, and the alerts that depend on it get lower confidence (Understanding confidence).

When sync fails

The Integrations page lists each run with its status (succeeded, partial, failed), counts and the error. Common causes:

Symptom	Likely cause and fix
“ERPNext rejected the API credentials”	Keys regenerated or user disabled in ERPNext → Control Center → Connection → enter the new keys.
“Could not reach ERPNext” / timed out	Network, VPN or ERPNext down. TaktSignal retries on the next run.
“denied read access to …”	A role permission was removed → restore Read for that document type.
Background updates stopped in the Control Center	The background process is not running → Help & diagnostics → Repair TaktSignal.

Nothing in ERPNext is ever changed by a sync, successful or not.