1

Hi

I’m having an issue with a recurring API workflow where it will run as scheduled, however, the API response is not updated with each refresh.

For example, I schedule it to check match status every 30 minutes and only take match data from Football matches only if the match status is ‘full time’.

However, when it checks every 30 minutes it only checks the initial response from the API, doesn’t generate a new one.

Any thoughts on how to resolve this would be appreciated:

Backend Workflow
Backend Workflow711×388 19.1 KB

Button Trigger
Button Trigger711×388 18.8 KB

2

Can you share your API connector setup as well please?

3

Screenshot below (in my API workflow, set the date to current date/time)

The the response from this works, as if I remove the recursive step from my API workflow and press the button each time, it refreshes the response - I’m just struggling to get the response to be taken at each scheduled API workflow after the initial button click

API Connector
API Connector799×287 10.6 KB

4

Are you setting the date in the current format in your backend workflow? In the YYYY-mm-DD format itself?

5

Yes, date is yyyy-mm-dd

6

To perhaps better explain

This is my challenge:

Aim
Aim1265×447 38.8 KB

Pictures of setup for what I can do:

Button Trigger
Button Trigger711×388 18.8 KB

Working

Pictures of setup for as close as I’ve been able to get to what I want:

Button Trigger
Button Trigger711×388 18.8 KB

Backend Workflow
Backend Workflow711×388 19.1 KB

I believe the issue is the ‘Football API - Get Football Results’ step only occurs once, however, I don’t know how to make this step recurring for each scheduled workflow:

Button Trigger
Button Trigger711×388 37 KB

7

I get it now - thanks for the details. You would ideally need to put this API call in your apitest workflow. Just keep in mind that you’re scheduling this on a list so better to be careful with the list size and whether you need to keep calling the API again and again.

In case you don’t need to, I’d suggest having a master/slave kind of implementation. Where the master backend workflow contains the first step as the API call, the second step as a SAWOL (the slave workflow) and third step as a recursive call, calling the master workflow again after a fixed interval in time.