Minor incident

Voyado: Engage - queue/buildup of some contact events

Affected: Automations, Other

Current status of Voyado: Operational — live Voyado status

Timeline

1. Oct 5, 2026, 13:16 UTC
   investigating
   There is currently a buildup of messages queued up on one of our processes, this is causing delays to automations triggered by interactions as well as webhooks related to contact events. It is being investigated.
2. Oct 5, 2026, 14:15 UTC
   identified
   We have identified a likely cause and taken steps to address it. We are now monitoring the results and will continue working on the issue until we can confirm it has been resolved.
3. Oct 5, 2026, 15:18 UTC
   monitoring
   We are seeing continued progress, with delays gradually decreasing. Delays remain, but we expect the service to recover during the evening. We will continue to monitor the service closely as it recovers.
4. Oct 6, 2026, 09:08 UTC
   monitoring
   Some delays remain. We currently expect the service to return to normal around 13:00 CEST and will continue to monitor it closely.
5. Oct 6, 2026, 12:47 UTC
   monitoring
   Unfortunately, some delays remain, but they continue to decrease. We currently expect the service to return to normal in about 30 minutes.
6. Oct 6, 2026, 14:09 UTC
   resolved
   This incident has been resolved. We have not observed any further delays since around 15:15 CEST.
7. Oct 13, 2026, 07:52 UTC
   postmortem
   ## Summary Between 5 October and 6 October 2026, processing of some events in Voyado Engage was delayed. The cause was an internal update to one of our background processes, which unexpectedly triggered a large amount of extra processing. The issue was limited to this process and has been corrected. ## Customer Impact Automations triggered by contact interactions ran later than normal. Webhooks for contact, consent and preferences changes were delayed as well. ## Root Cause and Mitigation A safeguard in the update did not work as intended, so existing data was processed again as if it were new. This happened on two occasions, 5 and 6 October. Our engineering teams stopped the process, cleared the extra processing and confirmed that everything was back to normal. ## Next Steps We are adding stronger safeguards and checks for this type of update, as well as earlier alerts so we can react faster if something similar happens. We apologize for the disruption and appreciate your patience.

Updates as published by Voyado (original).