{"version":"2.1.223","anchor":"telemetry-for-transient-background-job-state-read-failures","canonical_anchor":"telemetry-for-transient-background-job-state-read-failures","heading":"Telemetry for transient background-job state read failures","tier":"internal","area":"Background Jobs","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/telemetry-for-transient-background-job-state-read-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Telemetry for transient background-job state read failures\n\nBackground job state read failures now report themselves once per job instead of silently falling back to a cache.\n\n**What**\n\nA failed read of a background job's state now reports itself once per job before falling back to the cached copy, so intermittent storage problems are visible.\n\n**Details**\n\n- fires on backend errors and on parse\/read exceptions, and only if that job has not already reported\n- the event carries the errno and whether a cached state existed\n- oversized state files are skipped with a warning instead of being parsed\n\n**Evidence**\n\n`tengu_bg_state_read_transient`\n\n- Area: Background Jobs\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}