Activity is every long-running job your company has started, in one place: pack analysis, document processing, first drafts, evaluator reviews, clarification questions and submission exports. It is derived live from the same records the tender and knowledge pages render, so it cannot disagree with them.
Reading the page
Rows in flight lead the list whatever the filter. Each row names the job, what it is about (with a link), when it was requested, and an elapsed bar compared against the typical run time for that kind of job — never a percentage complete, because nothing can honestly claim one. The window (24 hours, 7 days, 30 days) and the filter (In flight, Failed, All) are in the address, so a view can be bookmarked. The rail's Activity badge counts what is running or queued.
The four states
- Queued — accepted, waiting for a worker. A queue wait shows as such rather than masquerading as work in progress.
- Running — picked up.
- Done — finished; the row links to the result.
- Failed — the job says why, in a sentence, on the row.
"Didn't finish"
A job that started and produced no result inside its window, with nothing still polling for it, is marked Didn't finish rather than left spinning forever. Document processing that stalls is re-queued automatically. AI jobs — pack analysis, drafts, reviews, clarification questions — never retry themselves: each run uses paid capacity, so a retry is always your click, on the card the job belongs to.