Feature Request: Pause and Resume Automations

[DavidDurman]

Role

User

Goal

To pause running automations, apply changes, and resume without downtime.

Reason

Currently, to make changes to an existing automation, a user must stop the automation entirely, which results in downtime and potential disruption of services. Users are seeking a more flexible solution that allows them to modify their automations without interrupting their operation.

Acceptance Criteria

• The user should be able to pause any currently running automation directly from the UI.
• While an automation is paused, the user should have the ability to make and save changes to the automation.
• The user should be able to resume the paused automation from the point it was paused, without losing the context or current state.
• No downtime is experienced by the end services due to the pause-resume operation.
• The system should log all pause and resume activities for audit and troubleshooting purposes.

Test Case

Title: Pause-Resume Automation Functionality
Objective: To verify that users can pause an automation, make changes, and resume it without causing any downtime.
Setup: Pre-create an automation with a simple task that is easily verifiable when running (e.g., sending a templated email to a designated address at regular intervals).
Steps:

• Navigate to the automations dashboard and identify the target automation.
• Initiate the 'Pause' action on this automation and confirm the action.
• Verify that the automation's status changes to 'Paused' and that it stops performing its scheduled tasks.
• Make a minor editable change to the automation (such as modifying the email template content).
• Save the changes and initiate the 'Resume' action on the automation.
• Confirm the 'Resume' action and check the automation's status for 'Running'.

Expected Result: After resuming, the automation should continue performing its tasks as per its configuration, including the changes made during the pause phase, without any downtime or interruption of service, and the modified task should be reflected in the subsequent operation (e.g., the changed email template content should be sent).