Resolved
This incident has been resolved.
Identified
The issue has been identified and a fix is being implemented.
Investigating
We have implemented a bypass on the affected component as we continue to investigate the root cause of this issue. All messages are currently processing in real-time with no delay, and there are no queued workflows to drain.
Investigating
We've discovered that a subset of workflow triggers that were sent to Knock today from 2am UTC may have been delayed in being processed, leading to delayed notification generation.