You are viewing limited content. For full access, please sign in.

Question

Question

Delay Activity doesn't trigger on time.

asked on October 15, 2021

We have a process we use that requires a very short wait time at the beginning of a workflow. In the past, we used the SDK activity to perform this wait. However, LF has said that this approach was unadvised. Instead, we have been using the workflow Date and DateTime tokens in order to get the start time, and adding 5 seconds to that time.

https://answers.laserfiche.com/questions/58027/Delay-Feature--Workflow--Delay-by-Seconds#58055

 

This has proven inefficient, as the wait activity will take an extra 20-40 seconds to resume the rest of the workflow.

Does anyone have any suggestions on how to improve this process? I understand that Workflow most likely does not check for Wait conditions every second, but the inconsistency as well as the extra delay makes this a poor user experience.

0 0

Replies

replied on October 15, 2021

Delay activity does not consider seconds. The timer's smallest interval is 1 minute.

The 20-40 seconds are likely the queueing time for processing. Can you explain what you're trying to achieve? Workflow is asynchronous, work gets queued and executed as soon as possible, but a delay is not guaranteed to be exactly as long as specified.

0 0
replied on October 15, 2021

The Workflow is querying the ResumeID from the FormsDB. The task is not assigned until after the workflow is started, so we are adding a small delay in order to give Forms time to add the row before querying the table.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.