aglinxinyuan opened a new issue, #5782:
URL: https://github.com/apache/texera/issues/5782
### Problem
When workflow execution **initialization** fails, the error is recorded into
the execution metadata store but is **never delivered to connected frontend
clients** — the user sees no error in the UI even though the execution failed
to start.
### Root cause
`WorkflowService.initExecutionService` wraps execution construction + start
in a `try`/`catch`. The catch arm only calls `errorHandler(e)`, which records a
`WorkflowFatalError` into the execution metadata store. It does **not** push
anything to `errorSubject`, the workflow-level websocket channel that
`connect()` subscribers listen on.
For failures during `new WorkflowExecutionService(...)` — i.e. *before*
`executionService.onNext(execution)` publishes the execution — no subscriber is
ever attached to that execution's metadata store, so the recorded error stays
invisible to the UI (it is only logged server-side).
```
init fails -> errorHandler records fatal error in metadata store
-> (no push to errorSubject)
-> frontend connect() subscriber receives nothing [X]
```
### Expected
Init-time fatal errors should reach the frontend the same way other errors
do:
```
init fails -> errorHandler records fatal error
-> errorSubject.onNext(WorkflowErrorEvent(fatalErrors))
-> frontend receives WorkflowErrorEvent [OK]
```
Discovered while splitting #5700 (loop operators); the fix is independent of
that feature.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
