delaystart seems not working when adding to the workflow option

[lingzhangcb]

Hi all,
We've using delaystart (setting to 36hours), but seems not working - still running immediately when start the workflow
any potential misconfiguration or possible direction to look into?

Thanks a lot

[demirkayaender]

Thanks for reporting this. This is a popular feature and we will take this as high priority.

Could you please help us with

• the version you are using (client/cli and server)
• which client you are using
• and how you are suing

[Groxx]

To do a quick check on expectations:
When using delay-start you will still always have a workflow "running" immediately. Everything in Cadence works this way, e.g. crons always start "now" and never stop running (they just atomically restart when they finish), there isn't any way to say "start this later".

What delay-start does is it creates the workflow immediately, but it will not actually "do anything" until the delay-start-duration has passed. In the UI this looks like a workflow with only 1 event (in the grid/detailed view), and no decision tasks until later. It's just implicitly sleeping until the time expires (literally none of your code runs during this), then it'll start running your code normally.

Does ^ this explain what you're seeing? Or is it actually doing things (e.g. running your workflow code / activities / etc) at the wrong time?

[bowenxia]

Hi there. It seems work. I've tested the feature in 2 ways:

1. Integration test:

2. I ran a delayed helloworld workflow in cadence-samples repo:
   How it looks like in CLI:

How it looks like in UI: