Surveypal Says a Production Release Was Deployed but Only Partially Applied, and Automations for Submitted Events Did Not Trigger Correctly

In an incident report posted on its status page on April 13, 2026, Surveypal said a production release of April 10 "was deployed but only partially applied." Part of its infrastructure kept running an older version, automations for submitted events did not trigger correctly, and some customers experienced missing automation triggers. The release was fixed on April 13.

Surveypal posted an incident report on its own status page on April 13, 2026, headed "Partial failure to trigger automation with on submitted condition." On April 10, it says, "a production release was deployed but only partially applied." Parts of it follow, not the whole.

Illustration

Deployed, but Not Everywhere

"Because part of the infrastructure continued running an older version, automations for submitted events did not trigger correctly," the postmortem says. Some customers "experienced missing automation triggers after submitting answers." The issue affected only the part of the system that remained on the older version.

Under "Root cause," it says that "The production release did not complete successfully across all infrastructure components. This left part of the environment running outdated code, which caused the automation logic to behave unexpectedly." The resolved entry on the same page says that "An unnoticed delivery failure caused part of the infrastructure to continue running the old code."

Deployed and applied are two different claims. The release was deployed. It was not applied everywhere, and the report itself calls the delivery failure unnoticed.

The Fix, and What It Says It Is Improving

The deployment issue was fixed on April 13 at around 15:00, the report says, and the missed automations "were reprocessed for the affected answers." Under the heading "What we are improving," it says the company is "focusing on" one area: "stronger checks that confirm all components are running the intended version."

What check would have shown that part of the infrastructure was still running the old code?