BeyondERP.Newsletter
Menu

Setup step on the Message queue setup page · System administration

Set message retention per queue

Decide how long processed and canceled messages are kept.

Used by
Scale unit administrator, Information technology manager
Business process
Administer system features
Menu item
SysMessageQueueSetup
Main table
SysMessageQueueSetup
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 setup page where you set, per message queue, how many processor tasks it uses and how long processed and canceled messages are kept.
What you do hereUse this page to set how long processed and canceled messages are kept in each queue before they're deleted.
ExampleFor example, BEAT keeps processed Warehouse messages for 30 days and canceled ones for 60, with 2 processor tasks; after saving, the Cleanup job for the message processor appears as a daily background process.
Message queue setup 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

Business processAdminister system features
Menu pathSystem administration › Message processor › Message queue setup
Set up firstMessage processor messages Microsoft Learn
Used next byProcess automations Microsoft Learn
Related pagesMaintain diagnostics validation rule Microsoft Learn
In this process Review failed messages
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.

Setup steps on this page

Set message retention per queue

Decide how long processed and canceled messages are kept.

Steps from Microsoft

  1. Go to System administration > Message processor > Message queue setup.
  2. Select Edit and select a queue, or select Add and choose the queue in the Message queue field.
  3. Set Number of processor tasks.
  4. Set Days before processed message deletion.
  5. Set Days before canceled message deletion.
  6. Select Save.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExampleTable column
Number of processor tasksHow many processor tasks work on the queue (maximum 8; the minimum depends on the batch threads, typically 2).Microsoft Learn 2MessageProcessorsTasks
Days before processed message deletionDays to keep processed messages; 0 turns cleanup off.Microsoft Learn 30MessageDaysBeforeProcessedMessageDeletion
Days before canceled message deletionDays to keep canceled messages; 0 turns cleanup off.Microsoft Learn 60

Common errors and fixes

MessageWhat to do
Old processed messages are never deletedDays before processed message deletion is 0, which turns cleanup off, or the Cleanup job for the message processor is paused on Process automations. Microsoft Learn

Test checklist

  1. Add a row for the queue and set Number of processor tasks (maximum 8).
  2. Set Days before processed message deletion and Days before canceled message deletion.
  3. Save, then check after the cleanup period that older processed and canceled messages are gone from Message processor messages.
  4. Check that failed and queued messages are still listed.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set message retention per queueNon-zero cleanup days for every queue in use, so the daily cleanup job removes old messagesLearn: 0 turns cleanup off; with at least one queue set, the system creates a daily cleanup background process, and Optimization advisor flags messages older than 30 days.How long are processed messages kept?Leaving 0 days, so messages pile up and Optimization advisor keeps reporting aged messages.Test: Cleanup removes old messages

Feature management and licence

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

Microsoft Learn

Solution architect

5Design impact

Shared or per companyPer message queue: each row sets the processor tasks and cleanup days of one queue; queues you don't configure use a default. Microsoft Learn
Can it be undoneReversible: Values can be changed; deleted messages can't come back.
If you change it laterQueues you don't configure use a default value that you can override. Microsoft Learn
Technical architect

6Technical

Menu itemSysMessageQueueSetup Checked in Dynamics 365
FormSysMessageQueueSetup Checked in Dynamics 365
TableSysMessageQueueSetupChecked in Dynamics 365
Who can open itPrivilegesCleanup job for the message processor SysMessageCleanupSelfHealingOpportunityTakeActionProcess messages SysMessageProcessDutiesMaintain the runtime of scale units. ScaleUnitRuntimeMaintain SysMessageSelfHealingRuleMaintainMaintain system settings SysServerSettingsMaintain
2 security rolesScale unit administrator ScaleUnitRuntimeAdminInformation technology manager SysServerITManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itInformation technology manager SysServerITManagerScale unit administrator ScaleUnitRuntimeAdminGive people one of these roles. On this system, 2 roles can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=SysMessageQueueSetup
Data migrationLoad order: Message queue setup has no data entity in Data management, so it can't be loaded from a file or a configuration template. Enter the few queue rows by hand in each environment.Checked in Dynamics 365
Everyone

8Sources

To cite this step: SA-MSG-830, Set message retention per queue. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SA-MSG-830