Conversation
The worker and the MCP session Durable Object are wrapped with @sentry/cloudflare, handled errors that reach ErrorCapture are sent to Sentry tagged with their console trace id, and every call the bridge has to answer with "Execution lost" is reported from the front worker, since an isolate killed by its memory limit cannot report itself. Disabled while SENTRY_DSN is unset. Claude-Session: https://claude.ai/code/session_01VMqJkxznzTQaFVHHcttxpJ
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes for us
Executor (host-cloudflare) had no error reporting. Failures such as the session memory crash only showed as "Execution lost" for the caller and a warning line in Workers logs. They now land in the Sentry project
skywardai/executor.Change
@sentry/cloudflare(same pattern asapps/cloud).ErrorCaptureare sent to Sentry, tagged with the console trace id so an issue matches its Workers log line.MCP call lost: <reason>(session_resetorresponse_deadline). A Durable Object killed by its memory limit cannot report itself, so the front worker reports for it, through a hook added to the vendoredagentspatch.SENTRY_DSNis unset. The secret is already set onexecutor-cloudflare.Verified in production
Deployed from this branch. Forcing a Durable Object reset during a 40 s execution produced the Sentry issue "MCP call lost: session_reset" within seconds.
https://claude.ai/code/session_01VMqJkxznzTQaFVHHcttxpJ