Cycles limit on wait for status

[victory]

I did review this ticket:

Retry API call?

I have an API endpoint to a 3rd party that starts a process on their end. Then I have a 2nd endpoint that calls the status of that original request. I'd like to call that 2nd endpoint, and if the [state] property == 'In progress', then wait a bit, and re-run it. Eventually it will return 'Complete', or 'Approved' or something, and then I can move on down my branch. I'm using a branch and some code to implement the wait, but I can't connect the wait block back to the previous query because it "…

But my case is a little different as the time to complete can be days not mintues.

This is the workflow I want:

1. Create New Request for an Order.
2. Check status of Order
3. condition - if "completed" (or it's been a month) mark workflow completed and end the wf. If not wait 5 hours then try again(ie go to step 2). Keep trying for a
   month, then give up and complete the workflow with status failed.

I can't just have a sleep then point back to step two because it will create a "cycle", even though cycles seem like a very common workflow pattern.

Any Ideas how to implement a simple workflow like this?

Thanks

[ferret141]

Maybe I'm familiar with this, but what is a cycle in this context?

[victory]

It's the error that is thrown when you create a loop in a work flow step1->step2->step3->step1, error when setting step1 as a destination for step 3.

[lindakwoo]

@victory,
You could instead call the entire workflow again. So create your if/else branch and in one branch you can create a wait block of 5 hours, and after that triggerWorkflowAgain (trigger the same workflow you are in). In the other branch, you can just return or send an email, etc. However, I caution you to make sure your condition to stop this workflow is working and in place, or you run the risk of creating a never-ending, endless workflow.

Let me know if this works for you!

[lindakwoo]

@victory,
Just checking in to see if the above suggestion works for you.