Background tasks
A long request does not have to hold your screen. Send it to the background: it runs on the iyedy server, you keep editing or close the page, and the Assistant tells you when the result is ready or when it needs your answer.
On this page
Before you start
- A request that can run long: a design, a review, a threat model, a research across your library or a document. Questions and descriptions answer at once and do not go to the background; neither does a request with an image or a PDF, because iyedy never keeps the file.
- Credits left. A background run shows its budget before it starts.
Send a request to the background
- Start the request
Ask as usual, for example “Review the whole Claims Platform for reliability and draft the risks for the board.”
- Choose the background
When the Assistant shows its plan, select Run in the background. Its budget line reads like In the background · up to 2 helper runs · about 40 to 90 credits, never more than 120.
A request already running can go too: select Run in background on its card.
The panel confirms: Running in the background. You can keep working or close this page.
- Keep working
Edit the diagram, open another one, or close the page. The run works on the diagram as it was when it started.
- Open the result
The Assistant's status dot changes when the run needs you or is done (Assistant: a background result is ready). Open Background runs from the Assistant menu or the panel's ⋯ menu, then Open the result.
The result opens as a card in the diagram's conversation: findings, a draft or a proposal you check and apply as usual.
Helper runs and the budget
A research or document request may split its question into parts and hand them to helper runs that work side by side. The budget line counts them: how many at most, the credit range of the whole run, and the most it may spend. A background run never spends more than that figure, and never more than the credits you have left. See How the Assistant uses credits.
When a run needs you
A run that has a question for you, or a plan to approve, stops and waits; the status dot says Assistant: a background run needs you. Open it, answer, and choose to send it back to the background. A run that waits too long for its answer expires; ask again to start over.
Limits
- A few runs at a time. Each plan allows a number of background runs queued or running at once; past it, a new one is refused until one of them ends.
- Not everywhere. Where the server does not offer it, the list reads Background runs are not available here.
If it doesn't work
There is no Run in the background button
The request is a question, a description or a request with an image or a PDF: those always run in the panel. For a long review or research, start it as such (Review…, Research…), then choose the background on its plan.
“Assistant: a background run stopped”
Open Background runs to read why. When credits ran out, what the run found so far is kept; add credits or narrow the request, then ask again.
The run waited for me and is gone
A run that waits for your answer expires after a while. Ask again; the conversation keeps the earlier request so you can start from it.
More symptoms: Assistant troubleshooting.
Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.
What went wrong?
Don't write personal data.