Stale deep links: treat 404 as 'gone', not as a polling error
When a React page polls GET /resource/:id from a ?query deep link, and the data can be regenerated (the run or dataset is swapped), handle ApiRequestError status 404 separately. Clear the cached object and set a 'missing' flag rather than an error string, otherwise the old object stays on screen or the user sees a raw error. Keep the decision in a pure helper (jobId, latestResponse, missing404, viewerId) -> none|ok|missing|other so you can unit-test it without rendering. Check that the response id matches the requested id before trusting it, because the previous response can linger while the next fetch is in flight. If you add a separate notice Drawer next to an existing one, check what opens the existing drawer (e.g. Boolean(job || error)) and pass it null/null in the notice states, so two drawers never stack.