Safety & limits

Automation that spends your money needs brakes. MerchDash layers several, and none of them are optional.

The per-run change cap

A single run — automation rule, Smart Rule, or bulk action — stops recording changes at your account's max changes per run (default 25,000). A rule with an overly broad condition therefore can't rewrite your entire account in one pass; the run reports that it was truncated so you notice and narrow the rule. Adjust the cap in Settings — lower it for caution, raise it for very large accounts.

Evaluation budgets

Every run also carries generous execution budgets — on items processed, per-item metric reads, and total wall-clock time (an hour). Only pathological rules ever trip them; when one does, the run aborts with a clear error naming the limit, instead of running away. Scripts are also size-capped, and the language deliberately has no file, network, or system access — a rule can read your ads data and call the documented actions, nothing else.

Settled data by default

Rolling windows exclude the two newest, still-settling attribution days, so a rule never punishes a keyword for sales that simply haven't been attributed yet. This is a data-correctness guardrail as much as a feature — details in Attribution & settled data.

Review mode and the full revert trail

Rules in Review mode change nothing until you approve the run. Either way, every change lands in Change history with before/after values and a reason, kept forever — and any change or whole run can be reverted. Reverts are logged as their own linked entries, so the audit trail is never rewritten.

No-op protection

Applying a change always checks the live state at Amazon first and skips no-ops — pausing an already-paused keyword does nothing rather than recording a phantom change, even if MerchDash's synced state was briefly stale.