https://answers.axonivy.com/questions/3744/delayed-task-and-expiry-tasks-timing-is-not-correct-if-the-interval-is-smaller-60-seconds<p>Hi Axon.ivy Team,</p> <p>In our project, we have several use cases that we would like to use the Delayed Tasks or Expiry Tasks. Depends on the business needs, our delayed or expiration duration <strong>may be 30 seconds or less</strong>.</p> <p>However, we discovered that the duration <strong>does not work</strong> if it is smaller than 60 seconds. I had done our homework a little bit and discovered that the <code>WorkflowJob</code> which was the main module used to resolve expired or delayed tasks is scheduled to run periodically on every 60 seconds. This was done in <code>WorkflowManager</code>.</p> <p>I assumed this was done <em>by design</em> but it took me by surprise because I could not find anywhere mentioning this limitation. The interval, 60 seconds, is hardcoded and is not configurable like the <code>SystemTask.SearchJob.Interval</code>.</p> <p>Is there any recommended ways to overcome this limitation?</p> <p><strong>UPDATE</strong></p> <p>In our system, we want to communicate to a 3rd party system, namely ABC, via its RESTful API.</p> <ul> <li>The process starts when a User triggers a designated action on the UI. We then call the ABC's API to initiate a process on their system.</li> <li>Our system then have to poll ABC's API for result <strong>asynchronously</strong>.</li> <li>The ABC API requires that we have to poll for result at least after 30 seconds from the time the first request has been sent.</li> <li>We want to have at max 3 attempts to call ABC's API for checking the result. Each time will have an additional delay of 10 seconds.</li> <li>At the same time, the User UI may be also polling for the result. It is not required that they have to keep the UI open.</li> </ul> <p>Having the above requirements, we are using Signal to trigger the polling to ABC's API asynchronously. The Signal process makes uses of SYSTEM TaskElement whose DelayDuration set to <code>30S</code>. For triggering a retry, the process itself then send a new Signal with an additional delay duration.</p> <p>What would be your suggestion to implement such a use case then?</p> <p>Bump this up!</p> <p>Regard</p> <p>Jack</p>enThu, 04 Apr 2019 02:54:41 -0400https://answers.axonivy.com/questions/3744/delayed-task-and-expiry-tasks-timing-is-not-correct-if-the-interval-is-smaller-60-seconds/3762<p>To me this sounds like the perfect use-case for a 'Wait' intermediate event:</p> <ul> <li>once the user invoked the ABC api the element can poll at your pre-defined intervall : <a href="https://developer.axonivy.com/doc/latest/PublicAPI/ch/ivyteam/ivy/process/intermediateevent/IProcessIntermediateEventBeanRuntime.html#setPollTimeInterval-long-">https://developer.axonivy.com/doc/latest/PublicAPI/ch/ivyteam/ivy/process/intermediateevent/IProcessIntermediateEventBeanRuntime.html#setPollTimeInterval-long-</a></li> <li>after the 'Wait' event was received you can continue with a normal task (either signaled or standard)</li> </ul> <p>I know the samples and API is dated: but for instance the <code>ch.ivyteam.ivy.process.intermediateevent.beans.FileIntermediateEventBean</code> contains a sample...</p>Reguel WermelingerThu, 04 Apr 2019 02:54:41 -0400https://answers.axonivy.com/questions/3744/delayed-task-and-expiry-tasks-timing-is-not-correct-if-the-interval-is-smaller-60-seconds/3762https://answers.axonivy.com/questions/3744/delayed-task-and-expiry-tasks-timing-is-not-correct-if-the-interval-is-smaller-60-seconds/3745<p>Hi Jack</p> <p>In workflow processes delay and expiry times are normally weeks, days or hours. </p> <p>What is your use case that you need to set this to seconds? Are you sure you use the right concept for your use case?</p> <p>There is currently no workaround for this.</p> <p>Regards</p> <p>Reto Weiss, Axon.ivy Support</p>Reto WeissMon, 25 Mar 2019 15:46:34 -0400https://answers.axonivy.com/questions/3744/delayed-task-and-expiry-tasks-timing-is-not-correct-if-the-interval-is-smaller-60-seconds/3745