CloudWorks™ integration scheduled to run despite being marked "Inactive" or vice versa

If users modify the status of a scheduled CloudWorks integration within 15 minutes of its scheduled run time, the change may not take effect for that specific run. The integration will execute according to its status at the time the run was originally scheduled.

For example:

• Deactivating an integration close to its run time will not prevent it from running.
• Activating an integration close to its run time will not trigger a run that was skipped when the integration was inactive.

To ensure status changes take effect, modify the integration status at least 15 minutes before its next scheduled run. If the next run is less than 15 minutes away, wait for it to complete before changing the status.