Find what your Talent did
Use the Activity tab in Settings to see every run, read its receipt, act on what needs you, and work out why something failed.
Chat shows you the conversation. Activity shows you the record. Every piece of work your Talent runs, whether you asked in the browser, in a connected messaging channel, or a Routine fired on a schedule, leaves exactly one receipt here.
Open it
- Open Settings from the Manage group.
- Choose the Activity tab.
You see your own runs. Activity is personal history, not a workspace feed.
The four views
- All: everything, newest first.
- Needs you: only the decisions you can still take, such as an action waiting for your approval. If this is empty, nothing is blocked on you.
- Completed: work that finished.
- Failed: work that stopped. Start here when something did not arrive.
Narrow further by time (today, last 7 days, last 30 days, all) and by source (web, connected channels, Routines, actions). There is a search box for the run title and its summary.
What a receipt tells you
Open a run and you get the narrative first: what was asked, what your Talent did, what it produced. Underneath sits the technical detail, including the governed tool actions it took, the model lane it used, and what the run cost in credits.
Receipts are canonical. If Activity and your memory of a chat thread disagree, the receipt is right.
A run that started as a chat carries a link straight back to that exact conversation, so you can pick the thread up rather than starting over.
Act on what needs you
A run waiting on approval shows the decision inline. Approve it and the work continues. You can also allow that kind of action to run automatically from then on, and every automatic run still writes its own receipt, so choosing convenience never costs you the record.
An approval nobody answers eventually expires. It stays in Activity, marked as expired, because a run that stalled is information you need.
Turn a good run into a Routine
When a successful run contains real tool actions, Activity offers to promote it into a draft Routine you can schedule. The draft is a reviewable starting point rather than an exact replay: receipts do not keep the precise arguments your Talent used, so read the steps before you save it.
A worked example
A marketing lead's Monday "pull last week's CRM deals into a spreadsheet and post the highlights to team chat" Routine did not post. They open Settings, Activity, choose Failed and last 7 days, and find one run against that Routine with a setup failure: the CRM connection needs reconnecting. They fix the connection, ask their Talent to run it once by hand, then check Completed to confirm the spreadsheet and chat post both landed.
What to check
- Activity is empty. Check your filters first. A view plus a time range plus a source can easily exclude everything; clear them and start from All.
- You cannot find a teammate's run. Activity is per person. Ask them to open theirs.
- A run shows as failed with no obvious reason. Look for a setup failure on its Routine. A disconnected or re-authorised connector is the most common cause.
- A Routine has no runs at all. It may never have fired. Check the Routine's schedule, and check the workspace is not read only. See Fix a read-only workspace.
- Nothing loads. Each section reports its own error. Reload once, then contact support with the message shown.
Get notified when work finishes
Turn on browser notifications for finished work, read the bell for things that need you, and choose the right channel for long running tasks.
Emails from TalentOS
Which emails TalentOS actually sends, why email is not the channel to rely on, and how to fix an invite that never arrived.