Bulk edit rules

/rules list → multi-select → bulk Duplicate or Delete (client-side loop, one API call per rule). No bulk pause/resume/cooldown endpoint. Each rule writes its own audit entry.

Written By Salvatore Sinigaglia

Last updated About 5 hours ago

/rules list → multi-select → bulk Duplicate or Delete (client-side loop, one API call per rule). No bulk pause/resume/cooldown endpoint. Each rule writes its own audit entry.

Bulk edit rules

/rules list → multi-select checkboxes → toolbar actions: Duplicate and Delete. These are the only bulk actions: they run as a client-side loop that fires one API call per selected rule (POST /api/v1/rules/:id/duplicate or delete). There is no bulk pause/resume, bulk cooldown edit, or server-side batch endpoint. Each affected rule writes its own audit entry (rule.duplicate / rule.delete).

Who is this for

Rule owners managing 10+ rules. Especially common in agency setups (many clients, similar rule patterns per client).

When bulk actions make sense

  • Reorganization — bulk delete deprecated rules after migrating to templates
  • Fan-out from a base rule — bulk duplicate a set of rules to seed variants (then edit each per-account)

For pausing/resuming many rules at once, there is no bulk toggle — pause/resume each rule individually (see rul-113). Changing scope, conditions, actions, or cooldown is also per-rule.

How to use

Step 1: Filter the list first

/rules page → filter / search to narrow the list to what you actually want. Rule status is one of active or paused.

Step 2: Multi-select

Tick checkboxes in the leftmost column. Top header checkbox selects all in the current view.

Step 3: Pick bulk action

Toolbar appears when ≥ 1 rule selected. The two available actions are:

  • Duplicate — clone each selected rule (each clone is created paused, named Copia di <name>)
  • Delete — confirm modal, then delete each selected rule

There is no bulk Pause, bulk Resume, or bulk Edit-cooldown.

Step 4: Confirm

Both Duplicate and Delete open a confirm modal listing the affected rules.

Step 5: Per-rule processing

The bulk action runs client-side as a loop: it fires one API call per selected rule. Each rule receives:

  • Its own API call (POST /api/v1/rules/:id/duplicate or delete)
  • Its own audit log entry (rule.duplicate or rule.delete)

Because it's a per-rule loop, a failure on one rule doesn't stop the others.

Limits

  • Rate limiting: workspace-wide rate limits apply, and since it's one call per rule, very large selections make many calls
  • There is no server-side batch endpoint or bulk operation ID

Audit log

Each rule's change writes a separate audit entry (dot-notation):

  • rule.duplicate
  • rule.delete

Common patterns

Clean up deprecated rules

  1. Filter to paused rules
  2. Select rules no longer needed
  3. Bulk action: Delete

Seed variants

  1. Select a set of working rules
  2. Bulk action: Duplicate
  3. Edit each clone (rename, change scope), then activate

Common mistakes

  • Expecting a bulk pause/resume: it doesn't exist — pause/resume each rule individually.
  • Bulk Delete without checking audit needs: deleted rules' execution history may still exist for retention, but the rule itself is gone. Export first if needed for compliance.

FAQ

Which bulk actions are available on the /rules list?

Wevion's bulk toolbar offers two actions once you multi-select rules: Duplicate and Delete. Both run as a client-side loop that fires one API call per selected rule. There is no bulk Pause, bulk Resume, or bulk Edit-cooldown, and no server-side batch endpoint.

Can I bulk pause or resume many rules at once?

No. Wevion has no bulk pause/resume — pause or resume each rule individually via its toggle (see the pause and resume article). The only bulk operations are Duplicate and Delete.

How does a bulk action run under the hood?

It's a client-side loop: for each selected rule Wevion fires a separate API call (POST /api/v1/rules/:id/duplicate for duplicate, or the delete call). Because each rule is processed independently, a failure on one rule doesn't stop the others. There is no shared bulk operation ID.

Does a bulk action create audit log entries?

Yes. Each affected rule writes its own audit entry in Wevion — rule.duplicate for duplications and rule.delete for deletions (dot-notation). There is no combined bulk audit record.