FLO Performance Issues
While the system is under heavy load, FLOs may run more slowly than usual or get queued up to finish once the issues are resolved.
How a delay is handled depends on the type of FLO:
Monitor FLOs are FLOs that trigger when a scheduled check finds new application data, such as a newly added customer. Your FLOs may appear to run later than expected, but will still process any new data only once, e.g. if 10 new customers have been added since the last time the FLO ran, the FLO may check for new data late and/or may check a few times in quick progression, but it will still process all 10 new records only one time each.
Schedule FLOs are FLOs that run on a regular schedule, such as every Friday at 9am. Your FLO may start and finish later than expected. If FLOs are queued up waiting to run, then a FLO scheduled to run every 10 minutes may run 3 times in a row after 30 minutes, for example.
Real Time (webhook) and API Endpoint FLOs are FLOs that get called directly by another application. The calling application may get a timeout error if the delay is too long even though the FLO is in the queue and will finish after the delay. This may cause issues if the caller attempts one or more retries in which case the FLO will run multiple times and/or the caller depends on getting a return value from the FLO. Similarly, a Form FLO may appear to fail when the Submit button is pressed but the FLO will eventually run.
Additional Note: When the system experiences heavy load, it may also cause slowdowns with sign-in to the website and/or fetching dynamic fields for adding or editing an app action card.
For More Help
Check our status page for more details on specific incidents that could affect your FLOs. Contact your support representative for further assistance.