Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverted guard allows rejoining a deleted workflow
Medium Severity
Removing
deletedWorkflowIdRefreintroduces a race condition. When aworkflow-deletedevent fires,currentWorkflowIdis set tonull, buturlWorkflowIdstill references the deleted workflow (URL hasn't changed). The useEffect seescurrentWorkflowId !== urlWorkflowIdand immediately emitsjoin-workflowfor the deleted workflow. This also affects theoperation-forbiddenhandler, which will attempt to rejoin a deleted workflow onSESSION_ERROR. SinceonWorkflowDeletedhas no consumers to trigger navigation, this race will reliably trigger for any user viewing a workflow deleted by someone else.Additional Locations (1)
apps/sim/app/workspace/providers/socket-provider.tsx#L496-L512Reviewed by Cursor Bugbot for commit 95e02c2. Configure here.