A possible solution I'm finding is combining the loop and branch by stage actions. The default stage contains a loop checking the status. After the loop maxes out at 250, it exits the loop and is then directed to stage 2, which then directs it back to stage 1 where it starts the loop over again. 

I tested this with a simple incrementing variable, and it ran the through the process over 250 times. So my assumption (assuming no other limits) is that this could run through 12,500 times (250 loop limit X 50 branch limit).

I would still love to know if there's a recommended way to do this repeated check. 

Thanks!

@bsikes Without knowing the API capability it is hard to suggest the best option, could you split up the workflow and trigger a component workflow from Right Signature when the status changes. Otherwise as mentioned it could be a combination of loops and pause actions to get the desired result.

@leighburke In this case, it wouldn't make sense to split up the workflow. Depending on the status returned, we may want to kick back the workflow to an earlier stage to revise things.

You mentioned difficulties suggesting a best option without knowing the API's capabilities - Is there any context where a third party API could trigger something within an existing workflow instance, without that instance having to initiate the check itself (and thus need to be in a loop where limits are present)?

I've not played around much with the NWC API (Didn't seem powerful enough when it came with interacting with existing instances), but possibly there's a solution to this within the Task based API calls.  Rather than having the workflow loop through a check/delay, maybe this would work:

1. From the workflow, initiate something that requires a certain outcome before continuing on.
   
   
   
   
   
   1. In this case, it's using the Right Signature API to send a request for a signature
   
   
   
   
   
   



2. From the workflow, assign a task to a Nintex API User. 



3. From outside the workflow, continually check for the desired status or wait for a callback from the API indicating the workflow should continue. 
   
   
   
   
   
   1. Possibly a scheduled task on a server or some other scheduling program that doesn't have limits on the amount of times it will check.
   
   
   
   
   
   



4. Once the desired status is found, use the NWC Task API to complete the task, causing the Workflow to continue without every needing to loop through a continual check/delay. 

Any obvious holes in that plan?

@bsikes I was more referring to how the other signing service actions work, in which it gets sent for signing and waits for the completion. If it worked in similar way you could of potentially made an xtension(https://help.nintex.com/en-US/xtensions/Home.htm). In regards to your idea it sounds like something that should work.