Stuck AI sub-agents unblocked when users defer decisions

aalises

·Apr 2, 2026·#27959fix(editor): Await confirmAction in handleLater to prevent stuck sub-agents (no-changelog)

A race condition in "Later" actions caused sub-agents to freeze indefinitely — the fix ensures the backend actually receives the skip signal before the UI moves on.

When users clicked "Later" on AI sub-agent confirmation dialogs, the UI raced ahead and showed "Skipped" — but the backend never got the message. Sub-agents remained frozen at waitForConfirmation, unable to proceed or retry.

The fix ensures the API call completes before the UI updates. Now handleLater awaits the confirmAction request, and if something goes wrong, the interface rolls back cleanly — matching how "Continue" and "Apply" already worked.

Backend logging was also added to resolveConfirmation so operators can trace why a confirmation target wasn't found. The result: deferred decisions actually defer, and stuck agents can finally move on.

View Original GitHub Description

Summary

Fix fire-and-forget handleLater in InstanceAiCredentialSetup and InstanceAiWorkflowSetup: the confirmAction API call was not awaited (void store.confirmAction(...)), so the UI showed "Skipped" even if the backend never received the confirmation — leaving the sub-agent permanently stuck at waitForConfirmation
Now handleLater awaits the API call and rolls back UI state on failure, matching handleContinue/handleApply
Added backend debug/warn logging to resolveConfirmation for diagnosability