What happened
What this says
Current to 11 Oct 26Connector status showed active but stopped pulling records; BB-Demo reset rate limit issue, sync resumed.
Problem: Ticket system connector status showed connected but stopped pulling new records for several days. Handling: First response 448 minutes. Bethan diagnosed rate limit issue in logs; reset connector and restarted sync. Watch: Slow first response affected experience; stale data for multiple days indicates freshness risk.
Details
Updated 9 Oct 26Prioritynormal
Statusclosed
Categoryconnector_sync
Channelemail
First response (min)448
Helpdeskmade from
Trail
- created · Cian Farrell 2 Jul 2026 15:22Hi, the connector for our ticket system hasn't been pulling new records for several days. The status shows connected but no new data is coming in. Can you investigate?
- public_reply · Bethan Lister 2 Jul 2026 22:50Hi Cian, thanks for reporting this. Just so I've got this right: the connector status page shows connected and active, but you're not seeing new records load? Can you check whether the API credentials are still current on your end? That's usually the culprit. Let me know and I can check our side. Thanks, Bethan
- public_reply · Cian Farrell 3 Jul 2026 14:56Yes, that's right. We checked the credentials and they're still valid. We didn't make any changes on our end.
- public_reply · Bethan Lister 6 Jul 2026 10:51Got it. I've looked at our logs and found the issue, your connector is hitting a rate limit because the connection's not being refreshed properly. I've reset it on our end and restarted the sync. You should start seeing records come through in the next few minutes. Let me know if you hit any issues. Thanks, Bethan
- status_change · 10 Jul 2026 23:59
Helpdeskmade from