Resolved after 13 minutes, on October 9, 2025.
**Root Cause** The issue arose because the subscription plan records in production were missing a crucial field, leading to a failure in the system. This caused the interfaces to become inaccessible as they couldn't retrieve the necessary information. **Resolution** The solution involved reverting the changes that introduced the bug in the production environment, thereby restoring the system's functionality. **Action Plan** To prevent future occurrences, improvements were made to the error handling screen, a deployment was executed to enhance query resilience, and additional validation was implemented in testing to ensure subscription functionality.
Update timeline
- investigating Oct 09, 2025, 07:08 PM UTC
We are currently investigating this issue.
- identified Oct 09, 2025, 07:16 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 09, 2025, 07:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 09, 2025, 07:22 PM UTC
This incident has been resolved.
- postmortem Oct 15, 2025, 08:38 PM UTC
**Root Cause** The issue arose because the subscription plan records in production were missing a crucial field, leading to a failure in the system. This caused the interfaces to become inaccessible as they couldn't retrieve the necessary information. **Resolution** The solution involved reverting the changes that introduced the bug in the production environment, thereby restoring the system's functionality. **Action Plan** To prevent future occurrences, improvements were made to the error handling screen, a deployment was executed to enhance query resilience, and additional validation was implemented in testing to ensure subscription functionality.
Your product runs on more than Pipefy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services