BeyondERP.Newsletter
Menu

Setup step on the Message processor page · System administration

Schedule one message processor job per queue

Process each message queue on a fixed schedule.

Business process
Administer system features
Menu item
action:SysMessageProcessor
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA periodic job that processes the messages in a selected message processor queue, on demand or on a schedule.
What you do hereUse this periodic task to set up a regular schedule for processing each queue.
ExampleFor example, BEAT turns on deferred production posting, so the administrator creates one recurring Message processor job for the Production queue and one for the Warehouse queue, and checks Message processor messages for Failed messages each morning.
Message processor page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itWhen a feature that uses the message processor is turned on, for example MES integration, deferred production posting or Warehouse management only mode.
How oftenOn a fixed recurring schedule for each queue, plus on-demand runs when a queue must be cleared at once.
Batch settingsCreate one recurring batch job per message queue.
What the output showsQueued messages in the selected queue processed in the right order, ending in state Processed or Failed. Messages that stay Queued usually mean no job is scheduled for that queue.

Source: Microsoft Learn

Setup steps on this page

Schedule one message processor job per queue

Process each message queue on a fixed schedule.

Steps from Microsoft

  1. Go to System administration > Message processor > Message processor.
  2. In Message queue, select the queue to process. The queue depends on the feature that created the messages, for example Production for deferred production posting or Warehouse for packing slip posting at container close.
  3. On the Run in the background FastTab, set up the batch and schedule options.
  4. Set up one job for each queue you use, usually on a fixed regular schedule; you can still run any queue on demand.
  5. Afterwards, open Message processor messages, filter on the queue and look for messages in state Failed; select Log to see why they failed.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Message queueThe queue to process, which depends on the feature that created the messages.Microsoft Learn Production
Run in the backgroundOne recurring batch job per message queue.Microsoft Learn

Common errors and fixes

MessageWhat to do
Messages stay QueuedNo Message processor job is scheduled for that queue. Create a recurring job for it. Microsoft Learn
Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Schedule one message processor job per queueOne recurring job for each queue that a turned-on feature usesMessages are processed per queue; a queue without a job keeps its messages Queued.How are message queues processed?Scheduling one job with Message queue left at None.Test: A queued message is processed

Feature management and licence

Licence or add-inOn this system the page opens for Information technology manager and Scale unit administrator. No Feature management feature needs to be turned on for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyOne job per message queue: each run processes the messages of the queue you select, whatever feature created them. Microsoft Learn
Can it be undoneNo: Processed messages have already done their work, such as posting.
If you change it laterProcesses the messages of the selected queue, which can post journals, packing slips or shipment orders, depending on the feature that created them. Microsoft Learn
Technical architect

6Technical

Menu itemaction:SysMessageProcessor Checked in Dynamics 365
Roles to set it up and use itTo use itInformation technology manager SysServerITManagerScale unit administrator ScaleUnitRuntimeAdminGive people one of these roles. On this system, 2 roles can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:SysMessageProcessor
Data migrationLoad order: Message processor has no data entity in Data management, so it can't be loaded from a file or a configuration template. It is a periodic job; schedule one per queue in each environment.Checked in Dynamics 365
Everyone

8Sources

To cite this step: SA-MSG-810, Schedule one message processor job per queue. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SA-MSG-810