See which trigger fires an action and save pre-approvals that stick
Action cards and detail pages now name the live session trigger instead of a generic label, scope chips count what the action actually saves, and the editor no longer offers a pre-approval that blocks the save.
You set up an action, save it, and later come back to check what it does. The card said "On trigger", the scope chip said "1 collections", and one toggle in the editor made the save fail with an error that pointed nowhere.
Live session trigger names
An action that runs after a live session wraps up showed "On trigger" on its card and detail page, so you could not tell what set it off. Both now read "When a live session ends". The "Write meeting outcomes to Notion" preset is exactly this kind, so anything you build from it names its own trigger.
Scope chips that match the save
The scope chip on the action editor and the pills in the prompt bar counted in plurals regardless of the number, so a single collection read "1 collections". Counts of one now read "1 collection", "1 label", "1 concept", "1 spreadsheet". Digits group according to your interface language rather than your browser's, so a German interface shows the same grouping everywhere.
The editor's chip also described a different scope than the one saved. Knowledge you @-mention in the prompt gets folded into the action's scope on save, and the chip now counts it too. Clear the picker entirely and the chip reads "All files", which is what the action saves.
Pre-approvals the save accepts
The editor used to offer a pre-approval for Chief's own action tools. Switching it on and saving failed with a generic error, and nothing pointed at the collapsed toggle behind it. That toggle is gone from the editor, and if a restored draft or a preset still carries it, Chief drops it on save instead of failing.
Open an action you already created and the card, the chip, and the editor now describe the same thing you saved.