bug: Worker Liveness DEAD

[imdevopx]

Describe the bug

after starting workflow with parallel jobs, workers immediately turns Liveness to DEAD then after a minute or two it will go back to Alive again then workflow somehow successful but very slow. any ideas?

To reproduce

1. Run a workflow with loop and parallel jobs. see the workers in Worker Groups..
   our sample workflow:
   worker status:

Expected behavior

Worker Liveness = Alive

Screenshots

seeing the below screenshot after our workflow starts. is it a normal behavior that worker has Liveness DEAD if it's in used?

Browser information

No response

Application version

v.1437.1

Additional Context

No response

[rubenfiszel]

No it's not expected but most likely the workers died for some reasons and you should be able to get some more info inspecting the workers logs.

Please share a reproducible example with:

• the full flow that you used
• the specs of the infra that you used
• the docker-compose that you used (if using docker-compose)