Track execution and review close history

Purpose

Staff follow close progress and locate earlier close or reopen runs for review.

How It Works

Submitting an action takes the controller to its run page. The page follows active execution automatically. Each step includes its outcome and relevant produced records or skipped explanation. Attempt counts span retry jobs for the same run. Events provide an ordered execution history. A browser reload returns to the selected run rather than starting another action. Close History lets a reviewer filter and page through earlier runs. Unsupported filters return validation errors. Missing or foreign runs return not found. The console adds people’s names when Platform can resolve them.

Relationships

Close and reopen create the listed runs.
Recovery begins from failed execution on the run page.
A successful close links to its lasting record.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Each run exposes its steps, attempts and events.Reviewers locate requests and outcomes across the workspace.
Surfaces: consoleapi

Controls

29 controls apply, from the corpus control catalogue.

TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-DAT-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-AVL-001 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005

Permissions

Key	Checked at	Scope
`accounting.fiscal-periods.read`	api	tenant

Business Rules

9 rules, 7 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	The run view presents period context, ordered step states, cumulative attempts, failures, outputs and events in chronological order. proved by `ATS-ACC-CLS-013-01`, `ATS-ACC-CLS-013-05`, `TST-ACC-CLS-017`, `TST-ACC-CLS-021`	calculation	service	test services-accounting:modules/fiscal-close/tests/e2e/fiscal-close-runs.e2e.spec.js#lists the run’s events, oldest first
`02`must prove Proposed	A close run includes the readiness captured by its revalidation step. proved by `ATS-ACC-CLS-013-01`, `ATS-ACC-CLS-013-05`, `TST-ACC-CLS-017`, `TST-ACC-CLS-021`	policy	service	test services-accounting:modules/fiscal-close/tests/e2e/fiscal-close-runs.e2e.spec.js#carries the readiness evaluated in the close, and the period as closed
`03`must prove Proposed	The console refreshes queued and running runs every two seconds and reloads the selected run after browser refresh. proved by `ATS-ACC-CLS-013-02`, `TST-ACC-CLS-005`	policy	console	observed react-console:components/accounting/close/close-run-view.tsx:CloseRunView
`04`must prove Proposed	Run listing returns newest runs first with unit, year, kind and status filters, using pages from one to one hundred items and a default of twenty-five. proved by `ATS-ACC-CLS-013-03`, `TST-ACC-CLS-017`, `TST-ACC-CLS-030`	policy	api, service	test services-accounting:modules/fiscal-close/tests/integration/services/persistence/period-close-runs.queries.integration.spec.js#answers every run of the tenant, newest first
`05`must prove Proposed	Unknown kinds or statuses, invalid page sizes and malformed continuation identifiers are refused. proved by `ATS-ACC-CLS-013-03`, `TST-ACC-CLS-017`, `TST-ACC-CLS-030`	validation	api	test services-accounting:modules/fiscal-close/tests/e2e/fiscal-close-runs.e2e.spec.js#refuses an unknown kind with 400
`06`must prove Proposed	A run absent from the workspace, including a foreign run, returns not found. proved by `ATS-ACC-CLS-013-04`, `TST-ACC-CLS-017`, `TST-ACC-CLS-050`	validation	service, database	test services-accounting:modules/fiscal-close/tests/e2e/fiscal-close-runs.e2e.spec.js#answers 404 for the run in another tenant
`07`must prove Proposed	Run reading and console Close History require fiscal-periods read permission. origin: services-accounting:docs/milestones/ACCT-M4-contracts-and-events-for-commerce.md#Rulings recorded during the milestone proved by `ATS-ACC-CLS-013-04`, `TST-ACC-CLS-017`, `TST-ACC-CLS-050`	permission	api, console	test services-accounting:tests/unit/fiscal-close-permissions.spec.ts#is required by the fiscal close routes: close by the close, reopen by the reopen, read by every other
`08` Proposed	The console resolves returned user references through Platform and retains the identifier when a person cannot be named. proved by `ATS-ACC-CLS-013-07`, `TST-ACC-CLS-013`	policy	console	test react-console:lib/accounting/close/http-service.test.ts#names every user reference of an answer with one lookup, keeping the id when nobody can be named
`09` Proposed	The execution view reads at most one hundred jobs for a run, oldest first, with no continuation. proved by `ATS-ACC-CLS-013-06`	policy	service	observed services-accounting:modules/fiscal-close/services/persistence/fiscal-close-jobs.ts:listFiscalCloseJobsOfRun

Scenarios

Id	Given	When	Then	Provenance
`01`	September’s close is active.	The controller reloads its run page.	The page restores that run and displays subsequent progress.	test react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0617.spec.ts#ACT-ACC-0617
`02`	History contains both run kinds across two business units.	The auditor filters to one unit’s reopens.	The result contains that unit’s reopen runs in newest-first order.	test services-accounting:modules/fiscal-close/tests/integration/services/persistence/period-close-runs.queries.integration.spec.js#filters by unit and year

Planning

Implementation

Track execution and review close history ​

Purpose ​

How It Works ​

Relationships ​