Last updated on August 18, 2026
Recurrence is a frequency control in Tinx Connector. It determines how often a message definition or a notification is allowed to run within the broader job queue schedule. With recurrence enabled, Tinx Connector checks whether enough time has elapsed since the last run before processing it again. It does not allow processing the specific message or notification on every job queue cycle.
This gives you detailed control over sync timing for specific tasks. For example, you can let an order import run every minute while spacing out a less time-sensitive notification. You don’t need to change the underlying job queue configuration itself.
Job queues and recurrence
Business Central job queues run automated tasks in the background at a set interval. By default, the job queue processes every active message definition and every active notification template on each cycle.
Recurrence modifies this behavior for a specific message or notification. When the job queue runs, Tinx Connector checks each active message and notification with recurrence enabled. It compares the current time against its next allowed run time. If that time has not yet been reached, Tinx Connector skips it and checks again on the next cycle.
The main purpose of recurrence is to reduce how often a specific message or notification runs. When the job queue runs every minute, processing every active message and notification on each cycle creates unnecessary traffic. Some messages and notifications do not need that high frequency. Recurrence lets you set a longer interval for those while leaving others unchanged.
Where recurrence appears
Recurrence appears in several areas of Tinx Connector. The two most common are:
- The Job Document page of a message definition, accessed from a synchronization dashboard. Recurrence controls how often a specific sync message runs within the dashboard.
- The Notification Center Card page, where recurrence allows you to control how often notification emails are sent.
Recurrence on message definitions works for both inbound and outbound messages. You can enable it independently on each notification template and each message definition.
To set up recurrence on a message definition
Select Search (Alt+Q) in the upper-right corner, enter Synchronisation Dashboard List, and then choose the related link.
On the Synchronisation Dashboard List page, select the dashboard you want to configure, and then choose the View action.
On the Synchronisation Dashboard page, select the appropriate message definition, and then choose the Card action.
On the Job Document page, on the Recurrence FastTab, turn on the Recurring Job toggle.
Set the interval in the No. of Minutes between Runs field.
-
Set the Earliest Start Date/Time field.
Initially, the Earliest Start Date/Time field defines the moment when the message definition first becomes eligible to run. After each run, Tinx Connector updates the field to the time of that run plus the number of minutes entered in the No. of Minutes between Runs field. The field then holds the next earliest time the message definition is allowed to run, not the time of the run that just completed. On each job queue cycle, Tinx Connector compares the current time with the Earliest Start Date/Time field. If the current time hasn’t reached that value yet, Tinx Connector skips the message definition and checks again on the next cycle.
You can set up recurrence in a similar way on the Notification Center Card page. For more information, see Notification Center.
Example: Reducing recurrence frequency for Magento order updates
You might need to set up recurrence on a synchronization dashboard related to order processing, such as M2R_IN_ORDERS for Magento. The M2R-086 imports new webshop orders, and the M2R-087 converts the orders into Business Central sales orders. Typically, you run them every minute, because you want to import and convert new orders as quickly as possible. However, the orders that are imported but pending an update on the webshop to be ready for conversion are not updated that often. The M2R-0871-1 message definition that updates imported orders can run less frequently. For more information, see Enable webshop orders import.
The following screenshot shows the example Recurrence set up on the M2R-0871-1 message definition Update status / payment in Magento order list. In this case, the TINX NAS Inbound Mgt. job queue is set to 1 minute, and the M2R_IN_ORDERS synchronization dashboard has just run. Tinx Connector has updated the Earliest Start Date/Time to 8/3/2026 1:45 PM. This is the next earliest time the message definition is allowed to run. The TINX NAS Inbound Mgt. job queue processes all other message definitions on the M2R_IN_ORDERS synchronization dashboard every minute. However, with the recurrence of M2R-0871-1, the message definition is processed every 10 minutes. On each job queue cycle before 1:45 PM, Tinx Connector compares the current time with the Earliest Start Date/Time field. Because the current time hasn’t reached that value yet, Tinx Connector skips processing this message definition. Once the current time reaches 1:45 PM, Tinx Connector processes the message definition. It then updates the Earliest Start Date/Time field to 10 minutes past that run.
Related information
Job queues
Notification Center
Synchronization
dashboards
Key concepts in Tinx
Connector
Troubleshooting
checklist
Get help
from Tinx Support
Help us improve the documentation
We continuously update the Tinx documentation. This article was recently rewritten. Send your feedback to docs@tinx-it.nl to help us make it even better.