What happened
What this says
As at Fri 9 Oct 2026Circuit records from the customer database stopped syncing after 20:15 one evening. Alan Rennie identified that an API token had expired, regenerated it, and the connector resumed normal operation.
Problem: The customer database connector stopped syncing circuit records after 20:15 one evening with no error message.
Handling: Connor Webb asked Alan Rennie to check for source system changes. Alan identified an expired API token, regenerated it, and ran a manual connector sync.
Watch: Quick resolution. Low risk if API token rotation schedules are formalized.
Details
Updated 9 Oct 26Prioritylow
Statusclosed
Categoryconnector_sync
Channelweb
First response (min)896
Helpdeskmade from
Trail
- created · Alan Rennie 2 Sep 2025 15:49Some of our circuit records stopped coming through this morning. The last sync completed at 20:15 last night, but nothing has loaded since then. We haven't made any changes on our end. Can you check what's happening?
- Public reply · Connor Webb 3 Sep 2025 06:45Just so I've got this right, the connector stopped syncing records after 20:15 yesterday. Can you tell me which system you're connecting to and whether anything changed on your side? Thanks, Connor
- Public reply · Alan Rennie 3 Sep 2025 12:09It's the customer database feed. No changes from us. The last pull was clean.
- Public reply · Alan Rennie 3 Sep 2025 14:14Actually, I've just checked, our API token may have expired. Let me regenerate it.
- Public reply · Connor Webb 3 Sep 2025 15:17Good call. Once you've got the new token in place, give the connector a manual run and let me know if it starts loading records again. Thanks, Connor
- Status change · 23 Sep 2025 23:59
Helpdeskmade from