A slow-running job on the default batch queue is causing a separate custom job to stall behind it — how can that custom job be routed to run on a different, faster batch queue instead?

All FAQ questions / Platform, Aurena, and customization

Answer

This depends on how the background job is set up. If it's configured as a standard Background Job function under a Batch Queue's configuration, simply move that function's assignment from the default queue's configuration to the faster queue's configuration instead. If the job is instead created manually in custom PL/SQL code via Transaction_SYS.Deferred_Call, that method accepts an explicit batch-queue parameter — hardcode the desired faster queue's identifier in that call so the deferred job is routed there directly, rather than relying on whatever default queue assignment would otherwise apply.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions