{"version":"2.1.219","anchor":"sessions-record-a-parked-job-id","canonical_anchor":"sessions-record-a-parked-job-id","heading":"Sessions record a parked job id","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/sessions-record-a-parked-job-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Sessions record a parked job id\n\nSessions now remember which background job they were handed off to, and validate their timestamps more strictly.\n\n**What**\n\nSession metadata now carries the id of the background job a session was handed off to, and timestamp fields in the metadata reader are validated more strictly.\n\n**Details**\n\n- `parkedJobId` is written when a session is handed off to the background agents view and cleared when it returns\n- the reader parses it as an optional string\n- `startedAt`, `updatedAt` and `statusUpdatedAt` now go through a shared bounds check for finite, non-negative and below a maximum, replacing a bare typeof number test\n\n**Evidence**\n\n`parkedJobId`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}