I'm trying to figure out what would be the best approach to check a state on a remote app on constant interval before proceeding flow further,
Option 1 (loop through recreation of timers)
1) Process starts
2) API call creates the async job on the remote system, storing a variable with the created job id. (JOB_ID)
3) The intermediate timer only delays the flow, nothing else.
4) the 'job completed?' node get the job via the JOB_ID var and put the status on a var (STATUS) var, it also increment some counter stored as a process var too (COUNTER)
5) the exclusive GW has 3 edges, where each edge has a condition based on the STATUS / COUNTER to decide where to move next
in case of 'no' the flow is transitioned back to the timer, which creates another job with 1 minute delay and so on..
(Is it safe enough as this is going to create more and more timers)
Option 2 (using multi marker)
1) One time API invocation to create the job on the remote app
2) A sub process which is executed multiple X times sequentially, in case of job completion, a node can change the completion condition of the multi marker (is it possible? does it make sense?) so the other tasks will not run as there's no need.
3) When the sequence ends (whether all tasks were executed = execution exceeded or not), another GW could decide what to do next according to the completion state set by the sub process.
Does this make sense? are there any better ways to tackle this scenario ?
Thanks in advanced,