ProcedureFlow Outage History

Started Aug 19, 2026, 03:40 PM UTC· resolved Aug 19, 2026, 04:37 PM UTC

1. investigating Aug 19, 2026, 03:40 PM UTC

   We are currently investigating this issue.

2. identified Aug 19, 2026, 03:49 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Aug 19, 2026, 04:01 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Aug 19, 2026, 04:22 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Aug 19, 2026, 04:37 PM UTC

   This incident has been resolved.

6. postmortem Aug 19, 2026, 05:16 PM UTC

   Earlier today, some customers experienced degraded performance due to an issue introduced during a routine infrastructure update. A gap in our deployment process allowed system capacity to become overwhelmed during a period of peak traffic. Our team identified the issue and resolved it by addressing the underlying capacity constraints. We're reviewing our deployment procedures to prevent similar issues in the future. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jul 22, 2026, 12:12 PM UTC· resolved Jul 22, 2026, 01:34 PM UTC

1. investigating Jul 22, 2026, 12:12 PM UTC

   We are currently investigating slow/failing requests when saving edits to flows.

2. monitoring Jul 22, 2026, 12:47 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jul 22, 2026, 01:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 18, 2026, 03:20 PM UTC· resolved May 18, 2026, 03:37 PM UTC

1. investigating May 18, 2026, 03:20 PM UTC

   We are currently investigating this issue.

2. investigating May 18, 2026, 03:20 PM UTC

   We are continuing to investigate this issue.

3. monitoring May 18, 2026, 03:30 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved May 18, 2026, 03:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 10, 2026, 09:38 PM UTC· resolved Feb 11, 2026, 01:07 AM UTC

1. investigating Feb 10, 2026, 09:38 PM UTC

   We are currently experiencing global DNS resolution failures impacting our availability. The issue is related to upstream DNS infrastructure on AWS. Our team is actively investigating and working to restore normal operations. Further updates will be provided as we learn more.

2. identified Feb 10, 2026, 09:41 PM UTC

   Procedureflow has confirmed that there is global widespread DNS resolution failures impacting Procedureflow as well as services we rely on. We're actively working with our DNS provider (AWS) to resolve this issue. You may experience Procedureflow app and status page intermittently working.

3. monitoring Feb 10, 2026, 10:46 PM UTC

   Our DNS provider (AWS) has implemented a fix. We are seeing signs of recovery and continue to monitor.

4. resolved Feb 11, 2026, 01:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2025, 04:40 PM UTC· resolved Apr 23, 2025, 01:42 PM UTC

1. investigating Apr 22, 2025, 04:40 PM UTC

   We are currently investigating an issue where change requests are sometimes not opening/saving.

2. identified Apr 22, 2025, 05:13 PM UTC

   The issue has been identified and a fix is being implemented. We will continue to share updates as they become available.

3. identified Apr 22, 2025, 07:55 PM UTC

   We are currently experiencing an issue where customers are unable to create change requests (or save drafts via the "old" UI). This is affecting all customers. The issue is related to the database limit for storing changes in change requests. We’ve hit a threshold that prevents us from adding more records, which is causing an error in the user interface. There is no data loss of existing change requests. Our team is actively working on fixing this. We are running a data migration in the background to increase the limit. We expect this data migration to be completed around 11 PM Eastern today and then will perform additional steps in our resolution plan. Unfortunately, until this issue is resolved, you will not be able to create new change requests/save new drafts. We recognize that this situation has impacted your workflow, and we're taking steps to avoid similar issues in the future. We'll continue to provide updates here and share a postmortem once the issue is resolved. If you have any questions, please contact us, and we can schedule a call to discuss further.

4. identified Apr 23, 2025, 09:23 AM UTC

   The data migration has completed. We are working through additional steps to use the new migrated data.

5. monitoring Apr 23, 2025, 09:56 AM UTC

   We have completed all steps to fix this issue and are monitoring the results.

6. monitoring Apr 23, 2025, 09:57 AM UTC

   We are continuing to monitor for any further issues.

7. resolved Apr 23, 2025, 01:42 PM UTC

   This incident has been resolved.

8. postmortem May 02, 2025, 01:56 PM UTC

   From approximately 12:15 PM ET on April 22 to 6:00 AM ET on April 23, all customers were unable to create change requests due to a database issue. Editing existing change requests was mostly unaffected. ## Root cause One of our database tables reached the maximum number of allowed entries \(~2.1 billion\), preventing change requests from being created. The maximum number was reached due to growth of ProcedureFlow usage. Although we have monitoring in place for database limits, we underestimated the rate of growth and were only monitoring these types of limits infrequently. ## Resolution The issue required an urgent database migration to expand the ID capacity and restore normal functionality. The migration was completed successfully without any data loss, and system availability for viewing and editing existing data was maintained throughout. The database migration and related mitigation steps took approximately 18 hours to complete due to the large volume of data involved. Under normal circumstances, we would perform this type of migration gradually and without any customer impact. However, because this issue affected all customers and prevented critical functionality, we prioritized speed and executed the migration as quickly as the system would allow, balancing urgency with data integrity and stability. ## Improvements We've completed the necessary upgrades to prevent this issue from happening again and have made improvements to our monitoring and operational processes to enable faster detection and recovery in the future. For example: * We've implemented more frequent manual and automated checks for database table entry limits. * We're monitoring and planning upgrades for any legacy tables that have the ~2.1 billion entry limit. All newer tables in ProcedureFlow do not have this restriction. --- We sincerely apologize for the disruption caused by this issue and understand the impact it had on your ability to make changes in ProcedureFlow. We are committed to ensuring this doesn't happen again, and we are continuously working to make ProcedureFlow more reliable and resilient. We value your trust and appreciate your patience as we continue to enhance the reliability of ProcedureFlow.

Read the full incident report →

Started Feb 13, 2025, 06:20 PM UTC· resolved Feb 13, 2025, 06:53 PM UTC

1. identified Feb 13, 2025, 06:20 PM UTC

   ProcedureFlow is aware that it is loading, but not display pages correctly. We've identified the issue and are working towards a fix.

2. monitoring Feb 13, 2025, 06:39 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Feb 13, 2025, 06:53 PM UTC

   This incident is resolved. We apologize for the inconvenience this has caused.

4. postmortem Feb 13, 2025, 09:32 PM UTC

   On February 13 at 12:54 PM Eastern, a new deployment was made to ProcedureFlow. Some customers loaded ProcedureFlow without any styles \(CSS\) applied – effectively making ProcedureFlow unusable. Not all customers were impacted by this issue, however, due to the geographically distributed nature of ProcedureFlow. By 1:34 PM Eastern this issue was fully mitigated and all customers were able to use ProcedureFlow again. We identified that certain CSS files served by ProcedureFlow’s content delivery service were served with the same name but different content. This conflicted with ProcedureFlow’s Subresource Integrity protection, causing browsers to reject loading the CSS files. The CSS file names also include a hash of the content. When the contents of a file changes, so should the file name. But we identified an issue with a component used by ProcedureFlow to generate these hashes causing different content to lead to the same file name. Although this issue is mitigated and resolved, we are planning to implement several checks that prevent this type of issue from happening again and will continue to improve the reliability and resiliency of our service. We apologize for this disruption as we understand that ProcedureFlow is critical to your own operations. If you have any questions, please reach out to us: [https://help.procedureflow.com/article/28-contact-us](https://help.procedureflow.com/article/28-contact-us)

Read the full incident report →

Started Nov 18, 2024, 08:29 PM UTC· resolved Nov 18, 2024, 09:30 PM UTC

1. investigating Nov 18, 2024, 08:29 PM UTC

   ProcedureFLow is currently experiencing issues. We are currently investigating the root cause; we will provide an update when we know more.

2. investigating Nov 18, 2024, 08:29 PM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 18, 2024, 09:07 PM UTC

   ProcedureFlow has been restored for at least the last 30 minutes; we will continue to monitor.

4. resolved Nov 18, 2024, 09:30 PM UTC

   This incident has been resolved.

Read the full incident report →