Skip to content
Documentation
DropUI homepage
Topics

Pause, edit or delete an automation

Need to pause communication or revise its content? Decide whether you are pausing the rule, editing settings or removing it from the current list. These actions affect pending steps differently.

Pause the automation

Open the rule's details and use the pause action. Confirm that it is no longer enabled.

Pausing stops further qualification and steps checked before dispatch. It cannot recall a message already accepted by the provider. Compare the pause time with message history if investigating an unexpected send.

Change its name or settings

Changing only the name preserves pending messages. Changing content, audience, timing or other sending settings stops pending steps from the old version.

Review what you intend to change. If you are only organizing the list, do not also alter the schedule or template.

Native local automation details with its state and available actions.

An enabled automation can remain enabled after saving changes. Pause first if you need time to prepare.

Resume deliberately

Check the sender, consent, data and content before enabling again. Activation does not arbitrarily catch up with old events. Each event and due time must still meet the scenario rules.

Use Check without saving and review an example before starting. A successful configuration check still does not prove delivery.

Remove an unused rule

Choose the delete action and read the confirmation.

Native confirmation for deleting a demo automation.

The removed automation leaves the current list and stops running, while execution history remains. This does not delete customers, orders or consent records. It also cannot recall messages already sent.

Have questions after reading this guide?

Get in touch. We’ll answer your questions and help you with setup, free of charge.

Patryk Surmacz

I’ll walk you through the settings, step by step.