Job Queue

Synchronization messages are processed in the background by a recurring Job Queue Entry, managed from the Jira Setup page.

Setting up the job queue

1. Open Jira Setup.
2. Select Initialize Job Queue to create the job queue entry. It runs the message processing codeunit as a recurring job, scheduled every day of the week, starting immediately.
3. Select Start Job Queue to set it to Ready so it starts processing on its configured schedule.
4. Use Open Job Queue Entry to open the job queue entry card directly, for example to change its schedule using the standard Business Central job queue fields, or Stop Job Queue to put it On Hold.
5. Select Refresh Status to update the Job Queue Status and Job Queue Last Run fields shown on the setup page.

astuce

The job queue entry uses the standard Business Central job queue, so it must run under a user with sufficient permissions, and the Business Central job queue itself must be active for the environment.

General settings

The General Settings section on Jira Setup controls how messages are processed:

Field	Meaning	Default
Refresh Threshold (Minutes)	How often the job queue entry runs	10
Default Priority	Priority used for messages whose entity configuration does not specify one	500
Max Retry Count	Maximum number of retry attempts for a failed message before it is marked Failed	5
Retry Delay (Minutes)	Delay before a message scheduled for retry is attempted again	5

The same Refresh Threshold also determines how long an access token can remain unused before the job queue proactively refreshes it, so tokens stay valid between runs.

What happens on each run

Every run:

1. Refreshes the OAuth2 access token for every enabled OAuth2 setup that needs it.
2. Processes pending and due retry messages in ascending Processing Priority order (lower number first) - by default, Organizations are processed before Customers, and other entity types follow the Default Priority.
3. Commits progress every 50 processed messages, and stops after 1,000 messages so a single run cannot block the job queue for too long; remaining messages are picked up on the next run.

A message that fails is either scheduled for Retry after the configured Retry Delay, or marked Failed once Max Retry Count is reached - see Understanding messages for the full set of statuses and how to act on them.

Message queue statistics

Jira Setup also shows Total Messages, Pending Messages and Failed Messages, each linking to the corresponding filtered view of the Jira Message Queue. The Navigate action group provides quick access to the Message Queue, OAuth2 Setup and Table Mappings pages.