Scheduled Script Deployments that Continue to Use Queues
For any scheduled script deployment created before SuiteCloud Processors, the Queue field still shows up by default. This goes for accounts with or without SuiteCloud Plus. The deployment record has a Remove Queue option you can use if you want to stop using queues. Once you pick it, the deployment won’t use a queue anymore—and you can’t switch back.
The Queue field is there for deployments that need FIFO processing from a specific queue. But all jobs—whether they use queues or not—are handled by the same processor pool and compete with each other using the same processing rules.
For deployments still using queues, make sure all jobs in the same queue have the same priority. Usually, the default (standard) priority works fine, but you can bump jobs in a queue to high priority if you always want a processor ready for them. Or, assign a bunch of lower-priority jobs to the same queue at low priority—they’ll run one at a time that way.
If your scripts rely on queue-based order (FIFO), update and test them before removing queues. Removing the queue could affect how your scripts run.
One workaround is to programmatically submit scripts in the order you want—use task.ScheduledScriptTask in the first script to kick off the second. This way, jobs reach the processor pool in the sequence you need.