You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
in my scenario, i have a task, which creates a subtask. when the subtask fails at some point (enters FATAL_ERROR state), the parent task is not updating and is stuck in WAITING state forever.
To Reproduce
to reproduce, i created dummy parent and sub tasks to illustrate the problem:
parent task:
Expected behavior
i expect the parent task to enter FATAL ERROR state when a subtask enters FATAL_ERROR
uTask version impacted by the bug
v1.28.X and up
Context which you are currently running utask
Inside a Docker container, running the official docker image, through docker-compose provided by you.
Additional context
i also tried previous versions (1.21 and 1.23) of uTask and the latest version.
if this is a feature, i would very much like to know how to control this behaviour, as i could not find and example or way to handle this.
The text was updated successfully, but these errors were encountered:
Describe the bug
in my scenario, i have a task, which creates a subtask. when the subtask fails at some point (enters FATAL_ERROR state), the parent task is not updating and is stuck in WAITING state forever.
To Reproduce
to reproduce, i created dummy parent and sub tasks to illustrate the problem:
parent task:
my-subtask:
Expected behavior
i expect the parent task to enter FATAL ERROR state when a subtask enters FATAL_ERROR
uTask version impacted by the bug
v1.28.X and up
Context which you are currently running utask
Inside a Docker container, running the official docker image, through docker-compose provided by you.
Additional context
i also tried previous versions (1.21 and 1.23) of uTask and the latest version.
if this is a feature, i would very much like to know how to control this behaviour, as i could not find and example or way to handle this.
The text was updated successfully, but these errors were encountered: