What happened
What this says
Current to 10 Oct 26Imogen Hartley reported nightly refresh sometimes extending into mid-morning, meaning her team lacks current data for early meetings on time-sensitive contracts. Callie Brennan offered to tune the refresh timing.
Problem: Nightly refresh scheduled for 06:00 was running into mid-morning on heavy data-volume nights, blocking the team's early standup and time-sensitive contract work. Handling: Callie confirmed the timing could be tuned and asked Imogen's target completion time. Imogen requested 07:00 on 11 Jul 2023. Watch: The service spec states nightly refresh must complete by 07:00 customer local time on business days. The evidence does not show whether the 07:00 target was achieved.
Details
Updated 9 Oct 26Trail
- created · Imogen Hartley 10 Jul 2023 14:08Hi Callie, a question on refresh timing. We've noticed the nightly refresh is sometimes not completing until mid-morning the next day, which means our team doesn't have current data for their early meetings. Our contracts are quite timing-sensitive. Is there room to tune this, or should we plan around a particular pattern? Best, Imogen
- public_reply · Callie Brennan 10 Jul 2023 23:11Hi Imogen, that maps cleanly to something we can tune. The refresh is scheduled for 06:00 customer local time, but on nights with heavier data volumes it can take longer. Before we switch on any changes, I need to know how much lateness you can absorb. What's the latest time you'd need the refresh to complete to work for your team? Thanks, Callie
- public_reply · Imogen Hartley 11 Jul 2023 16:38Thanks Callie – if we can get it done by 07:00, that gives us a clear hour before the main standup and means nothing's blocked the consultants. Does that timeline work from your side? Best, Imogen
- status_change · 11 Aug 2023 23:59