TroubleshootingReviewed 2026-09-29

Workflow rule, event type or message template cannot be deleted: runs, rules or actions use it

A workflow rule that has run is kept for its history and a system rule is never deleted or edited; switch them off instead. A custom event type that rules listen to, a message template that workflow actions or campaigns use, cannot be deleted either; deactivate it, or change what uses it first.

Messages this explains

  • “This rule has run before, so it is kept for history. Deactivate it instead of deleting.”
  • “Rules that have run before are kept for history and can only be deactivated.”
  • “System rules cannot be deleted; deactivate it instead”
  • “This is a system rule: switch it on or off, or clone it to change <fields>”
  • “Rules listen to this event type. Deactivate it or change those rules first.”
  • “An event type that rules listen to cannot be deleted; deactivate it or change those rules first.”
  • “Used by workflow actions; remove it from them first”
  • “Workflow actions use this template; change them first”
  • “That conflicts with existing data.”

Workflow rule, event type or message template cannot be deleted: runs, rules or actions use it

You tried to delete a rule, a custom event type or a message template under Settings > Workflows, and the app refused, or the delete button is greyed out.

What you see

Rules. Delete in a rule's row menu on Rules, or on the Rule page, opens "Delete rule?": "<name> and its actions will be removed. Rules that have run before are kept for history and can only be deactivated." When you confirm, a rule that has run at least once is refused with "This rule has run before, so it is kept for history. Deactivate it instead of deleting." While the rule is active, a Deactivate instead button appears under the message.

System rules (a purple "system" tag in the list) have no Delete at all, and their page is read-only. If a delete or change reaches a system rule some other way, it is refused with "System rules cannot be deleted; deactivate it instead" or "This is a system rule: switch it on or off, or clone it to change <fields>".

Event types. The bin on a custom event type on Event types opens "Delete event type?": "<name> (<code>) will be removed. An event type that rules listen to cannot be deleted; deactivate it or change those rules first." If it is in use, the dialog shows "Rules listen to this event type. Deactivate it or change those rules first." System event types (with a lock icon) have no bin.

Message templates. On Message templates the bin is greyed out while the Used by column counts any workflow action, with the reason "Used by workflow actions; remove it from them first" on hover. If an action started using it after your page loaded, the "Delete message template" dialog shows "Workflow actions use this template; change them first". A template that a campaign uses shows "0 actions" and its bin is not greyed out, but the delete fails with "That conflicts with existing data." System templates have no bin.

Why it happens

  • Runs are history. Every run records which rule ran, on which record, and what each action did: the emails sent, the tasks created, the demand runs started. Deleting the rule would leave those runs without their rule, so once a rule has run it can only be switched off. An inactive rule is kept but never runs.
  • System rules come with the organization. The seeded rules (reminders, follow-ups, the automatic demand and payout runs) are fixed: you switch them on or off, and to change one you clone it and edit the copy. This keeps the standard set intact and recognisable.
  • Rules depend on their event types. A rule set to On Event listens to one event type, and a rule can raise one with Emits event type. Deleting the type would leave those rules waiting for something that can never happen. Events already raised stay on the Outbox (processed ones for 30 days, failed ones until they are requeued and processed), and they block the delete too, with the same message, even when no rule is left.
  • Actions and campaigns depend on their templates. A Send email action that uses a message template, or a campaign that mails it, would have nothing to send. The Used by count covers workflow actions only, which is why a template used only by a campaign looks free until the delete is refused.

How to fix it

In the default roles only the Administrator holds the Edit and Delete permissions on Workflow Rules and the Delete permission on Message Templates; the Sales Manager can also edit message templates.

  1. Switch the rule off instead. Click Deactivate instead in the dialog, turn off the switch in the Active column on Rules, or untick Active on the rule's page and click Save changes (the Edit permission on Workflow Rules). For a system rule, press Switch off on its page. Its runs stay on Runs.
  2. To change a system rule, press Clone on its page (the Create permission on Workflow Rules), give the copy a name, change it, tick Active and Save changes, then Switch off the original so both don't run.
  3. For an event type, the easiest fix is to untick Active in its panel and Save changes: "Inactive event types are hidden from new rules; rules already listening keep working." To delete it instead, find the rules that use it (the Rules column counts listeners; on Rules, filter Entity and then Event type), change their trigger or event type or delete them, and clear it from any rule's Emits event type under Advanced. Events already on the outbox keep blocking the delete until they are cleared, 30 days after they were processed.
  4. For a message template used by rules, open each rule on the template's record type that has a Send email action using it (the template page reads "Used by <n> workflow action(s)."), choose another Email template or Write the email here, and Save changes. When Used by reads 0, delete the template (the Delete permission on Message Templates).
  5. For a message template used by a campaign, pick another Email template on the campaign while it is Draft or Scheduled (the Edit permission on Campaigns), or delete the campaign unless it is Sending or Sent (the Delete permission on Campaigns; see Campaigns). A campaign that is sending or has sent keeps its template for its log, so deactivate the template instead (next step).
  6. If you only want the template out of the way, untick Active on the Message template page and Save changes: "Inactive templates stay on existing actions but are not offered for new ones."

Related

  • RulesScreen

    Every automation rule in your organization, system and custom, with filters, the switch that turns each rule on or off, and shortcuts to edit, test, clone, see the run history of or delete a rule.

  • RuleScreen

    One automation rule's page: read or change its basics, trigger, conditions and actions, test it against a record, clone or delete it, and switch a system rule on or off.

  • Event typesScreen

    The named events a rule can listen to: the system events NirmaanOne raises itself and the custom events you add to chain rules or to raise from your own integrations.

  • Message templatesScreen

    The list of your organization's message templates: the wording that Send email actions and campaigns use, with filters and the actions to create, open or delete one.

  • Message templateScreen

    One message template's page: change its wording, attachments and settings, and preview it filled in for a real record.

  • RunsScreen

    Every time a rule ran: what started it, which record it worked on, how each action went, and the panel from which an errored run is retried.

  • CampaignsScreen

    The list of every email campaign with its status and recipient counts, the way into the campaign editor, and the link to the unsubscribe list.

  • Template, letterhead or generated document cannot be deleted: retire or void it insteadTroubleshooting

    A document template that produced documents, that an email template attaches or that a workflow rule uses is kept for history and is retired rather than deleted; a letterhead is deleted only once no template uses it; a generated document that was sent is voided, never deleted.

  • Workflow rules, conditions, actions and the rule ownerConcept

    What a workflow rule is made of (one kind of record, one trigger, conditions, ordered actions, an optional chained event), how conditions and action settings are evaluated, how versions, tests and clones work, and why every rule has an owner whose permissions its runs use.

  • System rules and starter templatesConcept

    The 53 automation rules, six email templates and six draft document templates every organization starts with: which ship switched on, why the customer-facing ones ship off, what is locked, and how to switch, clone or customise them.

  • Message templatesConcept

    The reusable wording of the emails that workflow rules, record-page buttons and campaigns send: a code, a channel, a subject and body with merge fields, an optional rich HTML body and up to five generated-document attachments, rendered against the record that triggered it.