Schedule history and reports

This covers the two drill-down screens you reach from the Security page: a schedule's full run history (/operation/security/:cronJobId) and a single run's report (/operation/security/:cronJobId/runs/:runId).

The full history screen

Open this by clicking View full history → on an expanded schedule card, or by clicking a schedule card's chevron and then that link.

• Loading: a centered spinner.
• Not found: if the schedule ID does not match any schedule you can see, "Schedule not found." with a Back to Security link.
• A ← Security link at the top returns to the main Security page.

The header

• The schedule's Title, with a "Paused" pill next to it if disabled.
• The schedule summary in plain language, plus · Next: <date, time> (or "Paused" if disabled).
• If you can manage checks:
  • Pause schedule (or Enable schedule if currently paused): toggles the schedule on the spot.
  • Run now: triggers an immediate run outside the normal schedule. Shows "Starting…" with a spinner while the request is in flight. On success, the run history list refreshes to show the new run. On failure (no credits, subscription past due, budget exceeded, service unavailable, or no permission), a toast appears with a specific message, and the list still refreshes.

Post results to communication channels

A card with a switch (on by default). Description: "Applies to scheduled runs only. Run now always stays inside ACE, and changing this does not close an existing thread." Disabled if you cannot manage checks.

Agent prompt

Shown only if you can manage checks and the schedule has a saved prompt. A collapsible Agent prompt section (click to expand or collapse) reveals the exact prompt text that gets sent to the agent on every run, exactly as written when the schedule was created or last edited.

Run history

The Run history section header shows a count badge for the number of runs, with a spinner next to it while the list is refreshing. Subtitle: "One card per execution — click for the full agent report."

• Empty: "No runs yet. Use Run now or wait for the schedule."
• Each run is a card, showing:
  • A status indicator: a spinner while pending or running, a red dot if failed, or a colored dot by severity once complete (red = critical, orange = high, yellow = medium, green = low; gray if no severity was assigned).
  • The run's title, falling back to "Running scheduled check…", "Scheduled check failed", or "Scheduled check" depending on state.
  • The run's source ID (monospace) and, next to it, "Running" (while active), "Failed" (if failed), or the run's type (once complete).
  • If the run failed and has an error message, it is shown in red below.
  • At the bottom: the run's source on the left, and a time-ago stamp on the right (or "In progress…" while active).
  • Clicking anywhere on the card opens its full report.
• The list polls automatically every 3 seconds while any run is still pending or running, so status changes appear without a manual refresh (this stops after about 100 refreshes for a given run).

What's in a run report?

Open this by clicking any run card in the history list, or a run row in a schedule card's expanded preview. URL: /operation/security/:cronJobId/runs/:runId.

• Loading: a centered spinner.
• Not found: "Run not found." with a Back to Security link (to the top-level Security page, not back to this schedule's history).
• A ← Security link at the top returns to the main Security page.

Header card

• The run's title, or "Running scheduled check…" while active, or "Scheduled check" as a fallback.
• Ran <date and time>, and, if set, · <run type>.
• The run's source ID in small monospace text below.
• On the right:
  • Linked issue / Create Card: see Creating a card from a report below.
  • Discuss in chat: shown whenever the run has loaded. Opens (or continues) a chat conversation scoped to this run and navigates you to it. Shows a loading spinner while the conversation is being opened. If it fails, red text appears below: "Could not open this scheduled check conversation."

Report body

• While running or pending: a large spinner, "Agent is running…", and the note "The full report will appear here when the check completes. This page refreshes automatically every few seconds." The page polls for updates every 3 seconds (up to about 100 times) until the run finishes.
• If the run failed: a red-tinted box: "This run failed before a report was produced." followed by the error message in monospace, if one was recorded.
• If complete with a report: the full write-up, rendered as formatted Markdown.
• If complete with no report content: "No report was produced", with the note "This run completed without report content. You can discuss the execution in chat or return to the schedule."

Creating a card from a report

On a finished run's report (not while it is still running), if you can manage security checks, can create issues, and the project is not in a read-only state:

• If the run has no linked card yet, a Create Card button appears. Clicking it opens "Create card from security report":
  • Title: pre-filled as [Security] <run title> (or a generic "Scheduled check follow-up" if the run has no title), editable.
  • Additional instructions (optional): a text area. Placeholder: "Add constraints or acceptance criteria. The schedule and full report are included automatically."
  • Cancel closes the dialog without creating anything (disabled while creating).
  • Create card is disabled until Title has text, and while the request is in flight. A failure shows red text with the error, or "Could not create the card." as a fallback. On success, the dialog closes.
• If the run already has a linked card, you instead see "Linked issue:" with either a clickable link to the card (if you can read issues) showing its key and title, or the plain text "Development card" (if you cannot).

Who can do this?

• security:read: required to view either screen.
• security:manage: required for Pause schedule / Enable schedule, Run now, editing the channel-posting switch, and (together with issue:create) for Create Card.
• issue:create: required, together with security:manage, for Create Card to appear.
• issue:read: required to see a linked card as a clickable link; without it you see "Development card" as plain text instead.
• Management actions and card creation also require the project to not be in a read-only or non-mutable state (for example a degraded project).