08-01-2024 12:32 PM
I’m working on a task that involves calling a REST GET request to check the status of a process. Once the status is marked as ‘completed’, I’ll need to trigger another REST GET request to proceed with the next step.Could you point on the best way to implement this?
Attaching below pipeline, highlighted section I am repeating the steps to make sure status changes to Complete before I trigger Zip File Read.
Tried has_next property like status!=‘completed’ and provide the next URL, but didn't work.
Your assistance would be greatly appreciated.Thank you!
Solved! Go to Solution.
08-07-2024 01:10 PM
@koryknick Using http client snap solved the issue
08-02-2024 07:33 AM
@deeps - you might want to check the return from that first REST Get - my guess is that you are still getting the document of the "non-completed" status check. So you will probably just need a Filter snap to discard the documents until the "Completed" status is returned.
Hope this helps!
08-03-2024 09:29 AM
@koryknick I tried filter snap and in RestGet added condition in Has Next section $entity.status!='completed', but for some reason it's not looping until condition is met, always status is in progress.
Note - When run in Postman status changes to complete within 30 seconds.
08-05-2024 05:40 AM
@deeps - please provide the output from your first REST Get- it is best if you can export it as JSON and attach the file to this post.
08-05-2024 06:35 AM
@koryknick I am attaching REST Get and Mapper output. Thank you