We have a scenario to call a reference playbook untill status is closed / Resolved with a specified interval.
Attaching reference playbook call step and execution history.
If you check execution history, it's iterarting with 5second interval instead of 300seconds
Can someone please help to resolve this issue?
I implemented a similar scenario with a 2-minute (120s) wait using a "do until" step, and it is functioning correctly for me(check the attached screenshot). However, it seems that your case involves a specific pattern that is causing the issue. Could you please check if your child's playbook contains any wait steps, such as "wait" or "manual input"? If it does, I suggest removing the wait from the child playbook, as the parent playbook will already introduce a delay through the "do until" loop.
Furthermore, it would greatly help me in comprehending the problem if you could provide a sample playbook that reproduces the issue.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.