Missed workflow notifications for checklist submissions - July 2026
Summary
Between 8 and 15 July 2026, some form submissions did not send the notifications customers had configured through Workflows.
Only workflows triggered when a form or template was completed or updated were affected. Other workflow triggers continued to operate normally.
We’re sorry these notifications were not sent as expected.
What happened
On 8 July, an improvement to how form submissions reached Workflows exposed an issue where answers from completed forms were not correctly checked against workflow conditions.
In some cases, a submission that should have matched a configured workflow was incorrectly treated as not matching, so its notifications were not sent.
Because the affected workflows did not report errors, our existing monitoring did not alert us. We identified the issue on 15 July following a customer report.
Resolution
We corrected the matching issue on 15 July and confirmed that subsequent submissions were triggering workflows normally.
We then audited all workflows that may have been exposed and identified affected events. We resent missed notifications where it was safe to do so and contacted customers directly where a notification could not be resent.
We completed this review and customer follow-up by 17 July.
What we are improving
We have added targeted automated tests for this specific issue.
Further work includes:
Additional monitoring to confirm that submissions matching workflow conditions result in the expected notifications.
Broader automated testing of the complete submission-to-notification journey.
A clearer escalation path for reports of missing notifications, so the right teams can investigate sooner.
No components marked as affected
Resolved
Missed workflow notifications for checklist submissions - July 2026
Summary
Between 8 and 15 July 2026, some form submissions did not send the notifications customers had configured through Workflows.
Only workflows triggered when a form or template was completed or updated were affected. Other workflow triggers continued to operate normally.
We’re sorry these notifications were not sent as expected.
What happened
On 8 July, an improvement to how form submissions reached Workflows exposed an issue where answers from completed forms were not correctly checked against workflow conditions.
In some cases, a submission that should have matched a configured workflow was incorrectly treated as not matching, so its notifications were not sent.
Because the affected workflows did not report errors, our existing monitoring did not alert us. We identified the issue on 15 July following a customer report.
Resolution
We corrected the matching issue on 15 July and confirmed that subsequent submissions were triggering workflows normally.
We then audited all workflows that may have been exposed and identified affected events. We resent missed notifications where it was safe to do so and contacted customers directly where a notification could not be resent.
We completed this review and customer follow-up by 17 July.
What we are improving
We have added targeted automated tests for this specific issue.
Further work includes:
Additional monitoring to confirm that submissions matching workflow conditions result in the expected notifications.
Broader automated testing of the complete submission-to-notification journey.
A clearer escalation path for reports of missing notifications, so the right teams can investigate sooner.
