What happened
What this says
Current to 14 Oct 26Nightly refresh failed when a data source connection timed out, causing dashboards to show stale data. Olivia Grant implemented a retry mechanism; refresh completed successfully by 24 Jul 2026.
Problem: The nightly refresh job failed on 21 Jul 2026 because a data source connection timed out. Dashboards blocked the recruitment pipeline tracking team. Handling: Olivia identified the timeout and escalated to engineering. A retry mechanism was designed and deployed on 24 Jul 2026. The nightly refresh ran successfully after deployment and data became current. Watch: This was part of a broader platform incident affecting multiple customers in July 2026. Monitor retry mechanism effectiveness and communication protocols during future incidents.
Details
Updated 9 Oct 26Trail
- created · Aisling Kiely 21 Jul 2026 09:53Our dashboards aren't showing today's data. The last refresh appears to have been yesterday morning. We rely on these updates for tracking our pipeline. Can you look into this?
- public_reply · Aisling Kiely 21 Jul 2026 10:01This is blocking our team from tracking pipeline activity. Can you look at this as a priority?
- public_reply · Olivia Grant 21 Jul 2026 10:24Thanks for flagging this and apologies for the impact. I can see the nightly refresh job has failed. Our platform team are being notified now and will investigate the root cause. I'll keep you updated.
- public_reply · Olivia Grant 22 Jul 2026 14:19I've been working with our engineering team on this. A data source connection timed out during the refresh, which stopped the full pipeline. We're implementing a retry mechanism to handle this. The fix should ship later today.
- internal_note · Olivia Grant 24 Jul 2026 10:32Fix deployed 06:45 today. Nightly refresh ran successfully last night. Data now current as of this morning.
- public_reply · Aisling Kiely 24 Jul 2026 14:54Thanks Olivia. We can confirm the dashboards are showing current data now. All good on our end.
- status_change · 31 Jul 2026 23:59