goto to a non-existent step id ends the workflow as 'completed' #20

New Issue

2026-09-08T20:57:27-04:00

jared commented

2026-09-08 20:57:27 -04:00

Overview

In executeWorkflowSteps() an unresolved gotoId logs goto_error and then breaks out of the loop, after which the function marks the execution completed. A mis-typed route target therefore produces a green ✓ in the UI, and the completion webhook fires, even though later steps never ran.

Suggested fix

Treat an unresolved goto as a failure (updateExecutionStatus(id,'failed') and return), and reject such definitions at save time (see the validation issue).

## Overview In `executeWorkflowSteps()` an unresolved `gotoId` logs `goto_error` and then `break`s out of the loop, after which the function marks the execution **completed**. A mis-typed route target therefore produces a green ✓ in the UI, and the completion webhook fires, even though later steps never ran. ## Suggested fix Treat an unresolved goto as a failure (`updateExecutionStatus(id,'failed')` and return), and reject such definitions at save time (see the validation issue).

jared added the bug backend workflow-engine priority/medium labels 2026-09-08 20:57:27 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/pulse#20