Troubleshooting Tip: Troubleshoot the issue with Schedule trigger

[jankit6]

Description	This article will help fix an issue where a schedule triggers multiple times, even if the 'Limit execution to one active instance at a time' option is enabled.
Scope	FortiSOAR.
Solution	The 'Limit execution to one active instance at a time' option prevents the schedule from triggering if the previous one is in an active state. If the system still triggers the schedule despite the active state of the previous schedule, try the following workaround: The issue could occur due to caching or incorrect entries in the database. Delete the schedule. Export the ingestion collection. Delete the collection. Reimport the playbooks and create a new schedule.