Tasks
Tasks is the durable work ledger for the selected township. It records work regardless of the trigger that created it.
- Console address
/townships/ :townshipId/ work/ tasks - Console section
- Township · Work
- Reviewed
- 14 October 2026
On this page
Controls and behaviour
Search and status filters narrow the collection. Pagination shows up to 50 tasks per page. Opening a task displays its journal and status. Agent and mission views can show the same ledger with a scope filter.
Access and limits
A task is not a single run. One task can have several attempts, waits or delegated steps. A visible task does not prove its provider writes succeeded; inspect effect and action records where those are relevant.
Field reference
| Field or state | Value | Meaning |
|---|---|---|
| todo | Task status | Recorded work waiting to be claimed. |
| in_progress | Task status | Work claimed for an execution attempt. |
| auth_required | Task status | Work waiting for an authority or human decision. |
| awaiting_effect | Task status | Work waiting for blocking effect evidence rather than repeating a write. |
| done, failed, cancelled | Terminal status | Work has ended. Its journal remains the record of reported progress. |
| Search, status, page | Console URL parameters | Filters the loaded task set and displays 50 rows per page. |
Related API endpoints
Console addresses and API addresses are different. These endpoints use authenticated console access and server-side authorisation.
/api/profiles/{profileId}/tasksDurable tasks. The console can supply agentId.
Related pages
Need more help?
Open Mysaria from the console header to ask about the page you're on, or send work to an agent in your township.