Resolved -
All the elements have caught up, and we are resolving this issue.
Mar 10, 12:05 EDT
Monitoring -
Due to the Daylight Saving Time transition, some batch event/actions did not trigger as expected on March 8. Affected event/types types include reading count (adherence), averaged threshold, and scheduled (pass_through) rules. Due to this, event/actions with daily frequency were not processed on March 8. Longer lookback rules that were not yet eligible to fire were unaffected.
A fix has been identified and deployed. Daily event/actions will be corrected today (March 9). Longer lookback event/actions will fully catch up by noon ET on March 10. We are also working to ensure any scheduled conversations that were missed are processed today, rather than waiting until their next scheduled window.
Mar 9, 14:53 EDT