Workflow settings
They exist to stop two problems: two workflows fighting over the same field, and workflows setting each other off forever.
- What the three settings do, and their defaults
- When to raise Priority
- Why to leave cascade depth alone
- What "once per record" is actually about
01 · Why
Why do we have these?
They exist to stop two problems: two workflows fighting over the same field, and workflows setting each other off forever.
02 · How
Press Settings in the builder.
| Setting | Default | What it does |
|---|---|---|
| Priority | 0 | If two workflows try to act on the same record at once, the higher number wins and the other backs off. 0 to 1000 |
| Maximum cascade depth | 5 | How many times workflows may set each other off in a chain before Merchaint stops it. Max 20 |
| Default once per record | off | Whether new steps should fire only once per record by default. Any step can override it |
Press Save.
03 · Notes
Raise Priority when two workflows disagree
If one workflow closes a record and another updates it, give the one that should win the higher number.
Leave cascade depth alone
Unless you have deliberately built a chain of workflows more than five deep. It is a safety net, not a feature.
"Once per record" is about repeats
With it on, a step that already ran for an invoice will not run again when someone edits that invoice. Good for notifications, bad for anything that should re-evaluate every time.
04 · FAQ
Common questions
Priority and cascade depth apply to the whole workflow immediately. "Default once per record" only sets the default for steps you add afterwards.
It declines to act on that record. It is not an error and does not stop the rest of the workflow.