Set up an automation paused and have it stay paused
Automations now run with the settings you saved them with: paused stays paused, web access stays off, and calendar-triggered actions say what fires them.
You set an automation up ahead of time, left it switched off, and it ran anyway. Or you turned web access off and the run searched the web regardless, spending credits you did not expect. Three changes bring automations back in line with what you saved.
Automations created paused
Asking Chief to set up an automation without turning it on, or creating one through the API with enabled: false, used to store it as running. The first scheduled occurrence fired, sent its outcome email, and spent credits. Now an automation you create paused stays paused until you switch it on yourself. Creating one from the web app still starts it enabled, as before.
Web access stays off
An automation saved with web access turned off still reached the web on its runs when its intelligence was left on Auto, even though its detail page showed the setting as off. Turning web access off now holds for the run itself, covering both web search and page reading.
Calendar trigger named on the card
An automation that fires on a new Google Calendar meeting, including the one from the Notion meeting pages preset, showed a generic "On trigger" on its card and detail page. You now see "When a new calendar meeting is scheduled", so you can tell at a glance what starts it.
Open your automations list to check the ones you set up earlier, especially any you meant to leave paused.