Agent Activity

QuantAssure uses AI agents for the work that takes judgement: triaging findings, assessing compliance controls, drafting questionnaire answers, assessing vendors and more. Reports & audit → Agent activity is the record of that work: every AI job that has run for your organisation, live while it is running and kept afterwards. The page is headed "Agent Activity" and described as "Monitor and review AI agent workflows".

Use it to check that a job you started is progressing, to see what a finished job produced, and to find out why one failed.

Reading a Job

Jobs are listed newest first, 20 to a page. Each one shows what kind of job it is, a status pill, and when it last did something. What else you see depends on its status.

Job statuses

StatusWhat it means
PendingCreated, not yet sent to the AI service.
DispatchedSent to the AI service, waiting for it to start.
ProcessingThe agent is working. A progress count and bar show how far it has got.
CompletedThe agent delivered its results, and they have been saved.
Completed with failuresThe job finished and delivered most of its results, but some items failed. The row says how many.
FailedThe job ended without usable results. The row says why, and what to do.
Timed outAn older way of recording a job that ran past its time limit. Newer ones are recorded as Failed with the reason.
CancelledThe job was stopped on purpose.

Pending, Dispatched and Processing together are the active statuses. The page checks for changes every 5 seconds while any job on the page is active, and every 30 seconds otherwise, so you can leave it open.

Active jobs

An active job is highlighted and shows a progress count such as 3/10 with a bar. Underneath, the figures from the AI service show how many items are completed, failed and pending.

Finished jobs

A finished job summarises what it did. For the main job types:

  • Finding Triage: "38 of 40 triaged", with a count failed and any compliance gaps found. Older jobs show "processed", "adjusted" (how many severities the AI changed) and "skipped".
  • ISM Assessment: how many controls were assessed, and how many were applicable and not applicable.
  • ISM Compliance: how many controls came out compliant, partially compliant, non-compliant or needing review.
  • Action Review: "Action review completed".

Jobs that deliver work in separate items also show "N of M delivered", with a red N failed pill and a grey N no result pill for items that never came back. A job can be Completed and still have a few failed items, so check the counts as well as the status.

Completed jobs have a link to where the results landed: View System for finding triage, View Controls for the ISM jobs and View Actions for action review. Other job types link to where their output lives, such as the vendors list, the risk register or the questionnaire.

Failed jobs

A failed job shows the reason in plain language with a suggestion, for example "The assessment took longer than expected and was stopped. Try running again, completed work is preserved." or "Could not connect to the AI service. Try again in a few minutes." If part of the work arrived first, the row adds "Partial progress: 4/10 callbacks received". When the cause isn't one QuantAssure recognises, the stored error is shown as it is, with any secrets redacted.

Jobs that stop making progress are failed automatically: the platform checks for stalled jobs every minute, and a job that passes its time limit is recorded as failed with the reason. The limits are 2 hours for the ISM assessments, 1 hour for finding triage and vendor assessments, and 30 minutes for action review, delta compliance, and the single-finding analysis and action jobs. Jobs of any other kind get 1 hour.

Filtering

  • Status: All, Active, Completed or Failed. Completed includes Completed with failures, and Failed includes Timed out. Cancelled jobs show under All only.
  • Job type: All, or any one of the job types in the table below.

Filters and the page number are kept in the page address, so a filtered view can be bookmarked or shared. With no jobs at all the page says "No agent jobs yet. Run an assessment or pipeline task to see activity here." If the list can't be loaded you'll see "Unable to load agent jobs".

What the Agents Do

Each job type is one agent doing one kind of work. Jobs are started either by something you do, or by QuantAssure on a schedule or after a system run.

Job (as listed)What the agent doesStarted by
Finding TriageReads each new or changed finding in your organisation's context and may reclassify its severity, with its reasoning.A system run
Compliance AnalysisCompares your policies with framework requirements and raises findings for missing or partial controls.A system run
RemediationDrafts prioritised remediation plans for findings.A system run
ISM AssessmentFirst-pass assessment of which Australian ISM controls apply to you.You, from Compliance controls
ISM ComplianceAssesses each applicable control against your policies, findings and assets.You, from Compliance controls
Delta ComplianceUpdates affected controls when triage changes findings that map to them.Finding triage finishing
Action ReviewConsolidates and prioritises queued potential actions, and dismisses duplicates.A schedule
Finding AnalysisThe on-demand analysis of a single finding.You, from the finding page
Action SynthesisDrafts an action for a single finding.You, from the finding page
Questionnaire Auto-FillDrafts questionnaire answers.You, by uploading a questionnaire
Vendor AssessmentReads a vendor's security documents and extracts risk findings.You, from a vendor
Risk Register SeedDrafts a first risk register for your organisation.You, from the risk register

Job types are shown by the names in the first column. A job type this page does not know yet is shown under its internal name in lower case.

Most AI jobs run one at a time for an organisation: if you start another while one is active, the second is refused until the first has finished. The on-demand single-finding jobs are the exception and can run alongside anything else.

Who Can Use It

Everyone in the organisation can open Agent activity, viewers included. Owners, admins and members also see Cancel job on a job that is waiting or running. You are asked to confirm, and the agent's work is stopped. Failed or cancelled ISM Assessment, ISM Compliance and Risk Register Seed jobs also have Retry, which starts a new job. Other job types have no Retry button: repeat the action that started them. Viewers see the page read-only.

How It Connects to the Rest of QuantAssure

  • Findings: triage results change a finding's severity and reasoning; see Your First Findings for how to read them.
  • Compliance: ISM jobs set applicability and control statuses, and the completed rows link to the controls.
  • Reports: the AI Decision Audit Trail report is the exportable record of what the AI decided.
  • Audit log: when a job completes, fails or is cancelled, the audit log records it.
  • AI allowance: every job counts towards your organisation's AI usage, shown in Settings.