---
id: SCR-PFM-QRY-006
title: Schedule detail and history
route: '/console/{tenantId}/queries/schedules/{id}'
surface: console
product_area: platform
module: queries
revision: 1
status: draft
design_intent: proposed
implementation_evidence: observed
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: >-
  Inspect a schedule’s source changes, pause reason and occurrence history with recipient delivery
  outcomes.
supports:
  - JNY-PFM-QRY-004
  - CAP-PFM-QRY-015
  - CAP-PFM-QRY-014
permission: platform.queries.read with platform.query-schedules.use (own) or .manage (any)
entry_from:
  - Schedules list
  - Saved query workspace schedule indicator
exits_to:
  - Schedule editor
  - the scheduled saved query or report
displays:
  - field: >-
      Source and owner, recipient list, file settings, recurrence, enablement and legacy-conversion
      marker.
    source: getQuerySchedule
  - field: Differences between the pinned question and its latest definition.
    source: getScheduleQueryChanges
  - field: 'Newest occurrence runs with file counts, recipient outcomes and download history.'
    source: listQueryScheduleRuns
actions:
  - label: Run Now
    operation_id: runQueryScheduleNow
    permission: platform.query-schedules.use
    confirm: true
  - label: Use Latest Query
    operation_id: useLatestScheduleQuery
    permission: platform.query-schedules.use
    confirm: true
  - label: Take Ownership
    operation_id: takeQueryScheduleOwnership
    permission: platform.query-schedules.manage
    confirm: true
  - label: Pause
    operation_id: pauseQuerySchedule
    permission: platform.query-schedules.use
    confirm: false
  - label: Resume
    operation_id: resumeQuerySchedule
    permission: platform.query-schedules.use
    confirm: false
  - label: Duplicate
    operation_id: duplicateQuerySchedule
    permission: platform.query-schedules.use
    confirm: false
  - label: Download a run’s file
    operation_id: downloadQueryExport
    permission: platform.queries.read
    confirm: false
  - label: Delete Schedule
    operation_id: deleteQuerySchedule
    permission: platform.query-schedules.use
    confirm: true
states:
  - detail loading
  - schedule missing
  - owner source access lost
  - latest question differs
  - source report deleted
  - legacy resume acknowledgement needed
  - no occurrence history
validation:
  - BR-CAP-PFM-QRY-015-03
  - BR-CAP-PFM-QRY-015-04
  - BR-CAP-PFM-QRY-015-05
  - BR-CAP-PFM-QRY-015-06
  - BR-CAP-PFM-QRY-015-11
  - BR-CAP-PFM-QRY-015-14
patterns:
  - Standard layout
  - section cards
  - run history table with expandable deliveries
  - query changes dialog
  - confirmation dialogs
component: 'components/queries/delivery/schedule-detail.tsx, run-history.tsx, query-changes-dialog.tsx'
evidence:
  - >-
    react-console at baf6dae: app/(console)/console/[tenantId]/queries/schedules/[id]/page.tsx;
    components/queries/delivery/schedule-detail.tsx, run-history.tsx, query-changes-dialog.tsx
controls: [TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-DAT-004, TC-DAT-005, TC-IAM-001, TC-IAM-002, TC-IAM-003, TC-IAM-004, TC-IAM-005, TC-IAM-006, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-005, TC-MON-001, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-TEN-004, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---

# Schedule detail and history

## What the Screen Is For

Inspect a schedule’s source changes, pause reason and occurrence history with recipient delivery outcomes.

## What It Shows and Lets People Do

The detail page supports eligible immediate runs, query refresh, ownership transfer, pause, resume, copy and deletion. Run history opens the produced file when available. Query schedules retain their pinned source until the person explicitly chooses the latest query.

## States and Errors

Report removal leaves only the supported deletion path. Imported recurrence requires confirmation of legacy shutdown. Source access loss is visible rather than granting execution through the schedule.

## Patterns It Must Respect

The standard-width page uses section cards and expandable recipient history. Query comparison and consequential actions use their existing dialogs.