Saving and checking studio rules

Open Automations to create a rule or edit an existing workflow. Choose the event that starts it, add conditions if needed, and connect the actions you want it to perform.

Save the whole rule

The workflow’s settings, steps and connections save together. Reopen the rule to check its event, field mappings and conditions before activating it. An inactive draft does not run on new work.

Supported actions include adding notes, changing records and moving work into production. Actions still follow the ordinary studio rules: a workflow cannot bypass material reservations, edit another studio’s records or delete protected order history.

Read the result

Open the workflow’s history to inspect a run. Completed, failed and skipped runs mean different things. A skipped run has not started its actions; a failure needs review before you assume the work was done.

When a rule updates stock, an order or a customer, open that saved record to confirm the result. Pause the rule while correcting its configuration if it should not run on new work.

Allowances and built-in work

Custom workflow runs have a monthly plan allowance. An admitted run can count even when its actions fail. Built-in workflows have their own included behavior, including the configured invoice workflow. Invoice numbers stay with their issued records rather than being reused.