BeyondERP.Newsletter
Menu

Setup step on the Change based alerts page · System administration

Schedule change-based alert processing

Turn logged changes into alerts for the users whose rules match them.

Business process
Administer system features
Menu item
action:EventCUD
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 reads the change-based events logged since its last run and creates alerts for those that match alert rules.
What you do hereUse this periodic task to process alerts for records that are created, deleted or updated.
ExampleFor example, if a rule watches customer BB and the name changes to AA before the job runs, no alert is created.
Change based alerts 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 › Periodic tasks › Alerts › Change based alerts
Set up firstAlert rules Microsoft Learn
Used next byNotification clean up Microsoft Learn
Related pagesDue date alerts Microsoft Learn Alert rules Microsoft Learn
In this process Correct a few records with an approved custom script · Schedule due-date alert processing
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 you start using alert rules for created, updated or deleted records; after that the recurring job runs on its own.
How oftenRecurring with no end date, for example every minute, balanced against system load.
Batch settingsRun it as a recurring batch job with no end date; lower the frequency if it adds too much load as more users create rules.
What the output showsAlert messages for every change since the last run that matches an alert rule. A missing message usually means the data changed again before the job ran, so the event no longer matched the rule's condition.

Source: Microsoft Learn

Setup steps on this page

Schedule change-based alert processing

Turn logged changes into alerts for the users whose rules match them.

Steps from Microsoft

  1. Go to System administration > Periodic tasks > Alerts > Change based alerts.
  2. Turn on batch processing, select Recurrence and set No end date with a pattern of Minutes and a Count of 1 when users need messages soon after a record changes.
  3. Weigh the interval: frequent runs deliver messages sooner but add system load, while rare runs can miss an event when the data changes again before it is processed.
  4. Make sure users have created alert rules for change events such as field updates, new records or deleted records; the job only compares logged changes with those rules.
  5. After it runs, change a record that an alert rule covers and confirm that the user receives the message.

Source: Microsoft Learn

Fields on the page

FieldWhat it means
Run in the backgroundTurn on batch processing and set Recurrence with No end date, a pattern of Minutes and a Count of 1 when users need alerts soon after a change.Microsoft Learn

Common errors and fixes

MessageWhat to do
No alert arrived although the record changedThe data changed again before the job ran, so the event no longer matched the rule's condition. Run the job more often. Microsoft Learn
The system slows down as more users create alert rulesEach run checks more rules. Run the job less often, at times of low load. Microsoft Learn
Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Schedule change-based alert processingOne recurring batch job with no end date, every minute where users need fast alerts, less often if load becomes a problemLearn: frequent runs give alerts sooner but add load; rare runs can lose alerts when data changes again before processing.How often does the change-based alert job run?Running it rarely to save load and then losing alerts because the data changed back before the run.Test: A change raises an alert

Feature management and licence

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

Microsoft Learn

Solution architect

5Design impact

Shared or per companyRules apply in the company where they were created, unless a rule is set to Organization-wide, which applies across legal entities. Microsoft Learn
Can it be undoneNo: Sent alerts can't be recalled; stop the job or change the rules to stop new ones.
If you change it laterRunning the job often gives faster alerts but can slow the system; running it rarely can miss alerts. Microsoft Learn
Technical architect

6Technical

Menu itemaction:EventCUD Checked in Dynamics 365
FormDialog Checked in Dynamics 365
Roles to set it up and use itTo use itInformation technology manager SysServerITManagerGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:EventCUD
Data migrationLoad order: Change based alerts has no data entity in Data management, so it can't be loaded from a file or a configuration template. It is a recurring batch job; set it up again in each environment.Checked in Dynamics 365
Everyone

8Sources

To cite this step: SA-JOB-870, Schedule change-based alert processing. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/SA-JOB-870