Workflow Maintenance Mode with Built-in Queueing - Make Maintenance EASY

The idea is:

To introduce a native “Maintenance Mode” or “Pause with Queueing” toggle for individual workflows.

When this mode is activated, the workflow’s trigger nodes (especially Webhooks) would continue to accept incoming events and immediately store their data in a built-in, internal queue. However, the rest of the workflow would not execute.

When “Maintenance Mode” is deactivated, the workflow would automatically begin processing all the events that were captured in the queue, ensuring no data is lost during the maintenance window.

My use case:

I have a critical production workflow that receives real-time order data from a webhook. Occasionally, I need to update the nodes in this workflow—for example, to change an API key for a downstream service, update the logic in a Set node, or handle a new data format.

Currently, I have to either risk losing incoming orders by deactivating the workflow, or I have to build and maintain a complex two-workflow queueing system using Google Sheets or a database. I want to be able to simply “pause” the main workflow for 10 minutes to safely make my changes, and then “unleash” all the orders that arrived during that time to be processed in the order they were received.

I think it would be beneficial to add this because:

This feature solves a critical operational problem for anyone running production workflows. The current workaround—building a separate queueing system—is complex, adds overhead, and introduces its own potential points of failure. I believe this is a feature that every single user needs.

A native “Maintenance Mode” would:

  • Prevent Data Loss: Guarantee that no trigger events are lost during routine maintenance or emergency fixes.
  • Reduce Complexity: Eliminate the need for users to build and manage their own complex, multi-workflow queuing solutions.
  • Improve Reliability: Provide a simple, one-click method to make workflows more robust and suitable for mission-critical, real-time applications.
  • Lower Barrier to Entry: Allow less technical users to confidently manage and update live workflows without fear of breaking data intake.
  • Enterprise-friendly: This is what large companies need

Any resources to support this?

Are you willing to work on this?

Sorry, not a developer but I have plenty of ideas that can make you more revenue and improve your PMF.