Prompt timeout silently continues the workflow; prompt/wait steps bypass the global execution timeout #21

New Issue

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

jared commented

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

Overview

When nobody answers a prompt within 60 min, executePromptStep() resolves null and the engine just moves to the next step (no log entry, no failed status, no notification). Steps after the prompt run as though the operator had approved them.
The global EXECUTION_MAX_MINUTES deadline is only checked at the top of the loop, so a single wait (up to 24 h) or a prompt (60 min) is never interrupted by it.

Suggested fix

Log prompt_timeout and fail (or route to a configurable onTimeout target); make wait/prompt timers respect the remaining global budget.

## Overview - When nobody answers a prompt within 60 min, `executePromptStep()` resolves `null` and the engine just moves to the next step (no log entry, no failed status, no notification). Steps after the prompt run as though the operator had approved them. - The global `EXECUTION_MAX_MINUTES` deadline is only checked at the top of the loop, so a single `wait` (up to 24 h) or a prompt (60 min) is never interrupted by it. ## Suggested fix Log `prompt_timeout` and fail (or route to a configurable `onTimeout` target); make `wait`/prompt timers respect the remaining global budget.

jared added the bug ux 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#21