Delayed execution of workflow

[caseyo]

Hi there! I’m working on a temporal workflow with the Java SDK, and I’d like to optionally delay starting execution of the workflow – potentially for a long period of time (on the order of days or weeks). The first thing I found and tried was Workflow.sleep at the beginning of the workflow implementation, but I wasn’t sure if I should sleep for long periods using that.

Is that the preferred way to delay execution of a workflow, or is there a better method?

[maxim]

Yes, Workflow.sleep is the way to go. There is no limit on how long the workflow is allowed to sleep giving that DB has enough space to keep all the sleeping workflows.

[rav223]

In the latest version of the Temporal SDK and with the latest Temporal server, you can use WorkflowOptions to specify the start delay.

[sshanzel]

With the start delay being available, which one is the better option now?

[antonio.perez]

@sshanzel thanks

I have responded to your post

Sleep vs start delay

For delaying execution of workflows, it was mentioned sleep is the way to go from this link. A year after that, start delay was introduced. Which is the better option now, and why? I am having the same use case from the linked post.