What happened
What this says
As at Fri 9 Oct 2026A key connector stopped loading after its API credentials expired. Bethan Lister identified the cause and asked Lee Hathaway to generate a fresh token from the source system.
Problem: Lee Hathaway reported that a key connector had stopped loading new records and that a restart had not fixed it. He said the matter was critical for the key account team.
Handling: The first response was logged at 224 minutes. Bethan Lister found that the API credentials had expired the day before and asked Lee to replace the token in the connector configuration. The ticket was solved on 14 May 2026 and closed on 18 May 2026.
Watch: The record does not show whether Lee updated the token or whether the sync resumed. The fix sits in the customer's own source system, so the sync may stall again when credentials next expire.
Details
Updated 9 Oct 26Trail
- created · Lee Hathaway 5 May 2026 17:08One of our key connectors has stopped loading new records over the past day. The last successful load was yesterday morning and I've restarted the connector once already but it's still not picking up fresh data. This is critical for our key account team, so we need this working again urgently. I've checked the settings from my end and they look correct. What should I try next, or can you investigate on your end?
- Public reply · Bethan Lister 5 May 2026 20:52Hi Lee, I've picked this up and checked the connector on our system. I found the issue: the API credentials expired yesterday, which is why the sync stopped. You'll need to generate a fresh token from your source system and update it in the connector configuration. Once you've done that, the sync should resume and new records should load through. Can you try that and tell me what you see? Thanks, Bethan.
- Status change · 18 May 2026 23:59