---
id: TST-PFM-QRY-230
title: Platform query schedules
kind: api-lifecycle
product_area: platform
module: queries
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  rhythm-v2-docs: 99376625d3e7ac26936413cfc31a88fba6562464
repository: services-platform
files:
  - modules/queries/tests/e2e/query-schedules.e2e.spec.js
implements:
  - ATS-PFM-QRY-011-12
  - ATS-PFM-QRY-015-09
  - ATS-PFM-QRY-015-12
  - ATS-PFM-QRY-015-13
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: 'The suite’s database fixtures, controlled execution contexts and file-owned external dependency seams.'
evidence:
  - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js'
assertion_bindings:
  - scenario: ATS-PFM-QRY-011-12
    source:
      - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#deletes the report'
      - >-
        services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#pauses the schedule
        report_deleted, its report gone
    scope: contributing assertions; the scenario combines multiple files
    provenance: test
  - scenario: ATS-PFM-QRY-015-09
    source:
      - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#refuses skip-when-empty (400)'
    scope: contributing assertions; the scenario combines multiple files
    provenance: test
  - scenario: ATS-PFM-QRY-015-12
    source:
      - >-
        services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#accepts Excel for a table
        report
      - >-
        services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#refuses Excel for a dashboard
        (400 at options.format)
      - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#refuses a CSV (400)'
      - >-
        services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#refuses a caller without
        platform.reports.use (403)
      - >-
        services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#refuses a replacement that
        would turn it into a query schedule (400)
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-015-13
    source:
      - >-
        services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#pauses the schedule
        report_deleted, its report gone
      - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#refuses to resume it (400)'
      - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js#refuses to run it now (404)'
    scope: contributing assertions; the scenario combines multiple files
    provenance: test
fixture_seams:
  - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js:115'
  - 'services-platform:modules/queries/tests/e2e/query-schedules.e2e.spec.js:161'
---

# Platform query schedules

## Verification Boundary

The file dispatches requests through the real route table and signed execution contexts against its local fixtures.

## What This Suite Proves

Its assertions check query schedules. The assertion bindings identify the corresponding acceptance examples and retain their original test-title citations.

## What It Does Not Prove

Local execution does not establish deployed queue scheduling, every external provider response or a passing result at the pinned revision.

## Real Dependencies and Test Doubles

The integration fixture and any imported dependency seams define the environment. Database-oriented checks use PostgreSQL; file-owned transport, clock, provider or worker seams isolate the explicitly controlled boundary.

## Must Not Be Doubled

Keep the dispatcher, route requirements and the handler behavior named by the assertions real. Review any new substitutions before treating the same acceptance bindings as unchanged.