Work queues question

Unknown

Work queues question

Unknown

1. Is there a recommended way to use work queues with scheduled jobs in order to prevent scheduled jobs from dominating system resources and hampering the performance of other work?
   These scheduled jobs are causing slowness across the board for this server? Or are causing other scheduled jobs to backup when certain jobs are running for long periods of time?
   The first thought that comes to mind is using the scheduled job as just a job loaded. So it runs, load the file/makes the API call/however you are loading the data into the flow. Then it spawns off a bunch of flows the appropriate queue(s) for each discrete thing being processed. Then the default job loader can take over working the list of those things and anyother launched processes using its logic instead of dumbly waiting for a long running synchronous flow to end before loading the next work.

2. Is there a way to queue up critical incoming queued flows (not scheduled jobs, but incoming requests) in such a way that that they’re handled with highest priority and other queued flows are handled when the critical events are depleted?
   You can get a flow to execute immediately if you give it a unique queue name. The idea here it seems is to use the default queue for all regular work and then have priority work create unique queue names so that they can be immediately executed. The below image is of an async subflow. When this flow is run it will spawn a number of discrete queues in the thread jobs report that will allow begin executing immediately and will not be affected by the queue order of the default queue.