"ASYNC: JDBCFileLoaderSensor" scheduler worker jobs run at priority 100, blocking more important jobsIssue The 3rd party "JDBC File Loader" app's "ASYNC: JDBCFileLoaderSensor" jobs run in the app node's scheduler workers at priority 100. Where a large batch of these jobs have been run in a short time, a big dump of these jobs can be added to the scheduler worker queue (sys_trigger) causing an instant backlog, of potentially hours. One of the problems with this is that these jobs run at 'normal' priority 100. For what is actually a low priority asynchronous background job, this priority is too high, because much more important out-of-box jobs at priority 100 or lower, can be delayed behind this backlog. That includes nearly all async business rules for record updates, that users are currently actively working on. Also, the important "MID Server Monitor" job, which needs to run every 5 minutes, is also priority 100, and can therefore be delayed behind this backlog. To put this into perspective, if this were a Discovery feature sensor, it would be running at priority 110.ResolutionThe solution, in that case, was to change the priority of the JDBCFileLoaderSensor business rule to 110:https://<instance name>.service-now.com/sys_script.do?sys_id=e393d9d96f0c35008a9810bd5d3ee4fc These jobs will still run, and still put the instance under considerable load, but will prevent more important jobs like async business rules for user updates and the MID Server monitor jobs from being stuck behind them.Related LinksLinks for the unsupported 3rd party JDBC File Loader code (that hasn't been maintained or verified for many years):JDBC File Loader (via MID Server)https://developer.servicenow.com/connect.do#!/share/contents/5711173_jdbc_file_loader_via_mid_server?t=PRODUCT_DETAILS