In this guide· 2 chapters
Every run leaves a receipt
Each time a workflow runs — on schedule, or because you tapped Run now — it opens a run: a timeline of its stages, top to bottom. You can watch it live as it happens, or read it back a year later. Nothing happens off the record.
Every stage on the timeline shows who did it, how long it took, and where it got to:
Done
The stage finished and handed its work on to the next.
Running
The agent is working on it right now — open it to follow along live.
Asking you
The stage paused and needs something from you. It is waiting in your 1Presence inbox.
Queued
Lined up, waiting for an earlier stage to finish first.
Open any stage to see what it worked from (inputs received), what it produced (outputs), the files it wrote to your vault, what it remembered, and any email it drafted. There is a transcript too, if you want to read its actual thinking.
While a run is going you are in charge of it. Cancel run stops it. Resume carries on a run that is waiting on you — or one that failed, from the stage that stopped, without repeating finished work. And Run now starts a fresh run any time.
When an agent needs you
Agents do not barge in. When one hits something only you can settle, the run pauses — politely — and a card appears in your 1Presence inbox: things your agents need from you. Answer it and the run picks up from exactly where it stopped.
Question
It asks something it cannot decide alone. Type a reply, pick one of the options it offers, or skip it for now.
Needs file
It needs a document to carry on — a contract, a spreadsheet, a brief. Drop the file in and it continues.
Approval
A yes or no before it goes ahead. Approve it, ask to see the run first, or decline.
Email to send
It drafted a message and held it for you. Review it, edit if you like, and send — or dismiss it.
Permission
The first time it wants to read an account or do something that reaches the outside world, it asks for the go-ahead.
Work stopped
A routine stopped for something only you can settle — an access it does not have, a file it cannot find. Its Sort it with button, naming the agent, opens a chat already holding the problem; settle it there and the routine runs again.
From a run
A finished run left you a note — a routine noticing its own work has changed, or a result worth a glance. Nothing is waiting on you; it reads as information.
One more card is not from a run at all: Shared with you, when a person shares a document with you by name and you can accept or decline. Each card tells you which agent, which workflow, which stage, and how long it has been waiting. You can answer right there, or open the full run timeline first. Answered cards drop into Already dealt with below — nothing is deleted — and a card you handled some other way can be settled with Mark resolved. Turn on notifications and you will get a ping on your phone the moment one needs you.
The inbox is also where you hear about work that is quietly changing. If a routine starts producing noticeably less, or drifting from what you set it up to do, a note arrives — a From a run card — saying so in plain words, with the likely reason already checked, like a connection that expired or a file that moved. Where there is a small, safe fix, it comes written out in full: what it says now, what would change, and why — yours to approve in one tap or dismiss. Changes to instructions you wrote always wait for your yes. And a routine that has clearly stopped doing its job is paused, never silently — the card explains why, and resuming is one tap.
Permissions: nothing leaves without your say
In a run, the first time a stage reads a connected account — your mail, your calendar — it asks once, and that answer is kept, so it does not stop each time after. The same goes for the first time a stage tries something that leaves a mark on the world — sending an email, posting somewhere, writing into a folder — it stops and asks, once, for that exact recipient or folder. You allow or deny; it remembers your answer; and you can take any grant back later.
This is why a workflow you have never run before will not surprise you. The consequential step waits in your 1Presence inbox the first time — and only the first time.
How a pause goes
- 1
A stage needs you
Mid-run, an agent hits a question it cannot answer, a missing file, or a step that needs your yes.
- 2
It waits in your 1Presence inbox
The run pauses and a card appears — on your phone too, if you have turned on notifications. Nothing else stalls; other work carries on.
- 3
You answer in a tap
Reply, attach the file, approve, or grant the permission — right from the card, or after opening the run.
- 4
It carries on
The run resumes from exactly that stage, with your answer in hand. No starting over, no lost place.
On your terms
It waits for you, not the other way around.
Runs pause politely, and only for the things that genuinely need a person. Everything else simply gets done and lands where you asked, with a timeline you can always read back.
Common questions
Q Where do I see what a workflow actually did?
Open its run. The timeline lists every stage with what it worked from, what it produced, the files it wrote and the notes it took — plus a transcript if you want the detail.
Q Will agents do things without asking me?
In a run, the first read of a connected account and the first attempt to send, post or write something out each stop and ask — for that exact account, recipient or folder — and remember your answer so it only asks once.
Q What happens if I miss a pause?
It just waits. The run stays paused and the card sits in your 1Presence inbox until you reply. Turn on notifications and you will get a nudge when something needs you.
Q Can I stop a run that is going wrong?
Yes — Cancel run from its timeline, whenever you like. A run only ever pauses on its own, to wait for you; Resume carries it on, and a failed run resumes from the stage that stopped.