Boney

Hi @dangjianguo123 - What version of Conductor are you using? @Sunyelw - Can you share the workflow definition? You can create it here and share - https://play.orkes.io (This is a...

Can you add your workflow definition to https://play.orkes.io/ ? We can evaluate your situation in that server. Alternatively you can share your workflow definition here and what level of concurrency...

Thanks for sharing the details, let me try and see if I can simulate this in our sandbox.

@LexiPow - for local testing you can add a host record on your local hosts file if you want to use anything other than localhost.

Hi @LexiPow - How are you running Conductor? Is it on a K8s cluster? If yes - you can add an ingress controller such as Nginx. Once you do, depending...

Hi @LexiPow - ping me on [slack](https://join.slack.com/t/orkes-conductor/shared_invite/zt-xyxqyseb-YZ3hwwAgHJH97bsrYRnSZg) if you can. I don't think I fully understood what you are stuck at. It looks like you are running this in your...

The default timeout is quite low. You might have to increase it. Here is an example of executed workflow in our sandbox: https://play.orkes.io/execution/ec899bc6-4538-11ed-8e05-4a68337b6f18 Definition to show timeouts: https://play.orkes.io/workflowDef/timeout_settings/1

@samox73 @tolikkostin We found a workaround for this in case it helps, we had to map all the env properties in the default env dir ("/run/etc/wal-e.d/env") to the clone env...

cc: @v1r3n

Hi @Nostras - this is sort of by design. The WAIT tasks are completed by the decision queues, which is scheduled once every 30 seconds with the default configurations. There...