Notifications and recurring tasks
The assistant doesn’t only work when you write to it. It also keeps an eye on the runs of your flows that fail and carries out on its own the jobs you have asked it to repeat. In both cases it only reads: what it prepares reaches you as a proposal and nothing changes until you approve it.
The bell
To the left of the Ask AI for Help button there is a bell. It is only visible while the assistant panel is closed. When it has something for you, the bell moves and shows a red counter with the number of pending proposals.
Click it to open the list of notifications:
- I spotted failures in your flows: fix proposals for flows that are failing.
- Your recurring tasks have news: the summaries from your recurring tasks.
- Your flows could cost less: cost-saving suggestions for your flows.
If there is nothing, you’ll see “No notifications. I’ll let you know here if I spot something in your flows or tasks.”
You can also ask in the chat: “what have you notified me about?” or “explain the notification about the invoices flow”. The assistant sees your pending notifications and answers you about them.
Fix proposals for failing flows
When a run of one of your flows fails in production (started through the API, a webhook or the Scheduler), the assistant reviews it on its own: it reads what happened in each component, looks for the cause and prepares a plan to fix it.
- One proposal per cause, not per run. If the same failure happens again, the proposal isn’t duplicated: it adds up “Failed N times” and updates the date.
- It doesn’t notify you about temporary outages of an external service that fix themselves.
- It doesn’t touch anything. The review is done without being able to change the flow; it only leaves the proposal.
- It doesn’t review the runs the assistant itself starts when testing, nor voice agent calls.
Each proposal shows the title, the flow, how many times it has failed and when the last time was. There are two types:
| Type | What you see | Buttons |
|---|---|---|
| It can be fixed by changing the flow | Show plan expands the Cause and What I would do, step by step. | Apply the fix, Dismiss and See execution |
| The cause is outside the flow (an expired key, a service that is down, a missing permission) | “This can’t be fixed by changing the flow, but I’ll tell you what you can do.” | Ask the assistant, Got it and See execution |
Apply the fix opens the flow and a new conversation in which the assistant reviews the run that failed and fixes the flow. That conversation works like any other: in Guided mode it will ask your permission to run the flow and for everything else. See execution takes you to the flow’s execution log.
If you dismiss a proposal and the same failure shows up again more than a week later, the notification comes back.
Cost-saving suggestions
Once a day, the assistant looks at what your flows have spent on AI models over the last 30 days and looks for concrete changes that make them cheaper. It works this out without spending anything: it is arithmetic on your usage and the price table, with no model call.
It looks for four things, node by node:
| Suggestion | When it suggests it |
|---|---|
| Switch to a cheaper model from the same provider | The node answers briefly (classifying, extracting, deciding) with an expensive model, and a lighter one would cost at least 40% less. |
| Make use of the prompt cache | Each call sends a lot of fixed instructions and almost nothing comes from the provider’s cache: turn on “Prompt Caching” (Anthropic), or put the fixed part first in the prompt and the variable part last (OpenAI, Gemini, DeepSeek). If the prompt starts with a variable such as {date}, it tells you which one to move. |
| Trim what goes in | Each call sends more than 20,000 tokens: less history, fewer retrieved chunks or a summary before passing it. |
| Reuse answers | Most calls seem to repeat the same question. It is a hint: check the execution log first. |
It only notifies you when the saving is worth it: at least 5 a month (in your account’s currency) or 20% of the flow’s cost. It leaves one suggestion per flow, with what it costs a month, the estimated saving of each change and the node to change. Show details expands everything. Each saving is worked out on today’s cost, so they do not add up.
| Button | What it does |
|---|---|
| Apply the saving | Opens the flow and a new conversation. The assistant recalculates the figures, looks at the node, explains the saving and the risk (a lighter model may answer worse) and asks for your go-ahead before changing anything. Then it offers a test run. |
| Dismiss | Removes it. It won’t be suggested again for 30 days. |
| See usage | Takes you to Usage. |
If the saving is no longer worth it (for example, because you already changed the model), the suggestion leaves the bell on its own. You can also ask in the chat “how do I make this flow cheaper?” or “which flow costs me the most?”: the assistant uses the same figures, including the suggestions below the notification threshold.
Recurring tasks
A recurring task is a job that the assistant does on its own, every so often. For example:
Every Monday at 9:00, review the week’s failures in my flows and prepare a summary with fix proposals.
Every day at 8:00, check whether there are pending approvals and tell me which ones have been waiting for more than a day.
This is different from scheduling a flow. If what you want is for a flow to run on its own every Monday, ask it to schedule it: that is created in the Scheduler. A recurring task is work for the assistant, not for a flow.
Create a task
Ask for it in the chat in your own words: what you want it to do and how often. The assistant asks for your permission, showing you the frequency and the time zone, before creating it. A task can run at most once an hour, and each person can have up to 5 tasks (your organization can change that number).
To change a task, tell it in the chat as well: “make the failure review on Fridays”.
What it does and doesn’t do
- It only reads. A recurring task runs with nobody in front of it, so it can’t change anything: not flows, not schedules, not your account. If it tries to make a change, it is denied and the task records it.
- What it prepares reaches you in the bell: a summary and, if needed, fix proposals that you apply yourself.
- It uses your assistant usage. If you have run out of usage for the month, the task doesn’t run and is marked “No credit”.
The tasks window
The calendar-with-a-clock button in the panel’s top bar opens Recurring tasks. For each task you see its frequency, its time zone, when the next run is and an Active / Paused switch. You can also:
- Run now: starts it right away. The summary reaches you in a few minutes.
- Latest runs: each run with its status (Running, Done, Failed, No credit or Skipped), how many proposals it left and whether it tried a change that was denied.
- Delete: click twice to confirm.
New task takes you back to the chat with the sentence already started: “I want a recurring task: every …”. In the corner you see how many tasks you have out of the maximum.
The summaries
Each summary appears in the bell with the name of its task and the date. The first lines are shown; Show the full summary expands it. Discuss it opens a new conversation to talk it over with the assistant, without taking you away from where you are, and Got it removes it from the list.
If your organization has disabled recurring tasks, the window says so and the tasks you already had don’t run.