How to make shorter interval for schedule trigger?
I have a list of jobs in db that needs to be updated once a 10s: I get bunch of ids and polls vendor API to get their statuses. I need to to it fairly frequently.
Interval schedule node told me that the lowest is 1m.
How can I do shorter intervals?
2 Replies
AI Support Bot Information
<@340786646574170112> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
You can achieve shorter intervals than 1 minute by implementing a loop within your workflow. Instead of relying solely on the Interval Schedule node, you can combine other nodes to create a loop that runs at the desired frequency.
Here’s a possible approach:
1. Initial Trigger: Use an HTTP Request or any other appropriate trigger to start the workflow manually or based on another event.
2. Loop & Delay:
- Use a Loop or For Each node to iterate over your list of job IDs.
- Within the loop, make an API call to the vendor and update the jobs based on the response.
- After each iteration or job processing, use a Delay node to pause the loop for 10 seconds. This will help in achieving your required update interval.
3. Schedule next run:
- At the end of the workflow, trigger itself again using capabilities such as a call-back endpoint to start the process over or chaining with another event that triggers this workflow.
4. Error Handling: - Make sure to include error handling to catch and manage any failed API requests or exceptions that might occur, so they don't stop the workflow unintentionally. This approach uses a loop and delay to simulate shorter intervals and can keep running continuously. You would essentially replace the scheduled trigger with logic that repeatedly calls itself after it completes, taking care of adhering to any constraints that your vendor API might have, such as rate limits.
4. Error Handling: - Make sure to include error handling to catch and manage any failed API requests or exceptions that might occur, so they don't stop the workflow unintentionally. This approach uses a loop and delay to simulate shorter intervals and can keep running continuously. You would essentially replace the scheduled trigger with logic that repeatedly calls itself after it completes, taking care of adhering to any constraints that your vendor API might have, such as rate limits.
BuildShip AI Support