What happened
What this says
As at Fri 9 Oct 2026Aaron Crowther reported the timesheet connector had stopped adding new records since Friday, though it still showed connected. The customer had updated its timesheet product, and the API address was unchanged.
Problem: Aaron Crowther said the timesheet connector showed connected but the record count had not moved since Friday. The customer had updated its timesheet product that day, and its IT colleague said the API address had not changed.
Handling: Bethan Lister said she would check the logs and asked whether anything had changed on the timesheet side. The ticket was solved on 5 Nov 2024 and closed on 9 Nov 2024, but the record does not show the cause or the fix.
Watch: A connector that reads connected while records stop loading points to a broken source, usually after the customer changed a system. Timesheet data has been stale since Friday.
Details
Updated 9 Oct 26Trail
- created · Aaron Crowther 28 Oct 2024 10:59The timesheet connector seems to have stopped bringing in new records since the weekend. Our system admin didn't change anything on our side as far as I know. Could you take a look? Aaron
- Public reply · Bethan Lister 28 Oct 2024 17:04Hi Aaron, I'm sorry to hear that. Just so I've got this right, the connector still says connected but the record count hasn't moved since Friday? Can you tell me whether anything changed on the timesheet side? I'll check the logs in the meantime. Thanks, Bethan
- Public reply · Aaron Crowther 30 Oct 2024 16:40Hi Bethan, we did update our timesheet product on Friday. Our IT colleague says the API address didn't change. Hope that helps.
- Status change · 9 Nov 2024 23:59