Job Health and Diagnostics

The job health table shows the most recent execution status for every scheduled job. Click any job row to load the last 10 run records for that job.

Job Name	Frequency	What It Does
`sla-check`	Daily	Marks cases as SLA-breached when deadline has passed
`exception-expiry`	Daily	Expires stale risk exceptions and reopens their cases
`retention`	Daily	Purges records older than configured retention periods
`alert-eval`	Hourly	Evaluates `score_increase` alert rules against exposure snapshots
`permission-scan`	Hourly	Scans all Confluence spaces and computes exposure scores
`content-scan`	Manual only	Runs regex detectors against page content

The table columns are:

Click any job row to expand its run history. The history table shows up to 10 recent runs with:

Started: Full timestamp of when the run began
Status: success / failed / running
Duration: How long the run took
Details: Error message (on failure) or job-specific statistics (on success, e.g., “breachedCount: 2” for the SLA check)

For deeper diagnostics beyond the UI, stream backend logs from the Forge CLI:

cd forge-app
forge logs

This streams real-time function logs from all resolvers, scheduled jobs, and async consumers. Filter by function name with the --function flag.

There is no UI button to manually trigger individual scheduled jobs. If you need to force a job run outside its schedule:

Content scan: Use the Start Scan button in the dashboard Scanning tab.
Retention: Use the Run Now button in Admin Settings → Retention tab.
All others (SLA check, exception expiry): These must wait for their scheduled trigger, or a developer can manually invoke them via forge tunnel in a development environment.

Title here