Is the execution of Scheduled Tasks still dependent
Yes, the Snaplex-based Scheduler still requires a periodic to the Control Plane. The Snaplex-based scheduler can operate through network disruptions, but is not guaranteed to continue running with Control Plane outages.
If the connection to the Control Plane is disrupted, does the scheduling continue to work as long as the nodes are running?
Yes. However, some Pipeline executions may require connectivity to the Control Plane to retrieve accounts, files, and libraries. Retrieving these assets from the Control Plane during a disruption may cause fail.
What happens during rolling restart?
The scheduling process is performed by the Snaplex node. During the cooldown state, the node heartbeat checks which node is the scheduler, and then the elected node synchronizes its Tasks with the C, changes the scheduler from standby to started, and begins running Scheduled Tasks.
If the scheduling node fails, are the Scheduled Tasks missed or queued?
Similar to the rolling restart, when a node fails, another node takes over in the Snaplex and executes the Scheduled Tasks. The Snaplex-based Scheduler uses the same 15-minute timeout for failed scheduled as the scheduling node is back online before the 15 minutes has passed, then the Tasks should not be missed, though they may be delayed.
Are cron jobs still supported?
information should I use to troubleshoot?
You can look at the Task history in the Task Details page to find the node on which the Task was scheduled. With this information, you can view the logs on the scheduler node to .
Does encryption work the same with the Snaplex-based Scheduler?
Yes, there is no change to the encryption of accounts.
If the Snaplex-based Scheduler feature flag is set to false for my Org, do I have to reset the flag to true to enable it at 4.26 GA?
Yes, you must enable the feature flag to turn on the Snaplex-based Scheduler. Feature flag settings at the Org level take precedence over the global setting in the 4.26 GA release.