Job Queues

Job Queues in Business Central allow you to schedule and automate specific reports and codeunits. You can configure these jobs to run once or on a recurring basis.

A Job Queue typically contains multiple entries, where each entry is a specific task or job that the queue manages and executes. Each entry includes information such as:

  • Which codeunit or report should be run

  • When and how often it should run

  • The category it belongs to

  • Specific parameters for how it should run


Tinx Job Queue Entries for Communication

Tinx uses dedicated Job Queue entries to manage communication between Business Central and your webshop. These jobs are labeled with the Category Code: WEBSHOP.

By default, the following Tinx jobs are created:

Job Description
TINX NAS Inbound Mgt (Codeunit 11205263) Handles incoming data (orders, customers, product updates) from the webshop to Business Central.
TINX Outbound Mgt (Codeunit 11205261) Handles outgoing data (stock updates, shipment info, etc.) from Business Central to the webshop.

Other Scheduled Tasks

In addition to the main communication tasks, the following reports can be scheduled to optimize performance and data maintenance:

Report Description
Report 11205251 – Remove Historical Data Deletes old entries from the Synchronization Ledger Entries table to prevent unnecessary database growth. You can set the number of days the data should be kept in the E-Commerce Setup. It is recommended to schedule this report once per day, outside working hours.
Report 11205267 – Reset Order Checks Useful if it sometimes takes a long time before a webshop payment is approved. This report resets the number of order checks to avoid stuck processes.
Report 11205290 – Check Finished/Error Jobs If a webshop task encounters an error, this report will reset the status of any tasks with the WEBSHOP category code, so they can be reprocessed.

Automatic Processing

Tasks scheduled in the Synchronization Dashboard will only be processed automatically by the Job Queue if the following conditions are met:

  • The task Status is set to Released.

  • The Processing Policy is set to On Timer.