How to throttle issue looping in Jira automation

[Richard A_ Michaels]

I have written a Jira automation which sends a web request to Zapier

The automation runs on a schedule every day at 8:00 AM ET and executes a JQL query to determine which tickets meet the criteria. 

I need to control how fast the automation loops over the issues to prevent more than a single Zapier call from being made within  the same second.

Any suggestions on how this can be accomplished?

Thanks,

Richard

[William Calesco]

Easiest way would be you editing the issue after the call, like adding a label or something in a field.

Then in your scheduled trigger, use the jql (YOUR JQL and YOURFIELD != value) So you only interact with issues that have not been called

[Richard A_ Michaels]

William,

I found my answer and it was right there all along

Thanks for your reply.

Richard

[Richard A_ Michaels]

@William Calesco As it turns out, that delay didn't do what I thought it would do.
I was expecting a 10 second gap between each call to the web request.  That was not what occurred.  It also turns out that the throttling was in Slack not Zapier.  However, if the 10 second delay in Jira Automation function as I had expected, there should not have been a need to throttle because of the 10 second gap.