UnhandledRejection: Non-Error promise rejection captured with value: Failed to get flattened block context: Block not found

[sentry]

We've seen a number of these issues since releasing the new runtime. A small number of users have reported blocks not starting or stopping. I suspect this is because of the backend document not being up to date with the frontend, and therefore the block is not found by the runtime

Sentry Issue: DESKTOP-FRONTEND-MH

UnhandledRejection: Non-Error promise rejection captured with value: Failed to get flattened block context: Block not found: b750be64-3662-4eae-a980-235819bef6ac

[BinaryMuse]

This exception is likely from the dev mode block context inspector, which tries to find the context for the focused block, even if it's just a paragraph etc

[ellie]

Sentry says it's happened for ~300 distinct users in production mode, so I think it must be happening elsewhere too :/

[BinaryMuse]

We look up the context in all envs, only don't display the floating window in prod

https://github.com/atuinsh/desktop/blob/main/src%2Froutes%2Frunbooks%2FRunbooks.tsx#L575

When I migrated this in b0ef095 useBlockContext started letting the error propagate; we should probably just conditionally render