Biz event/Automation not working

Hi ​@Harry  , 

Are you talking about a SaaS instance, or a local instance?

It affects some things I’d be cautious about checking/avenues you might have for checking.

(EG for local hosting: Are you using RabbitMQ? Were you on the legacy messaging service? )

My usual advice would be to disable all automation schedules , and turn on just 1 for say, send/receive email and confirm if that schedule runs successfully.  

Are there errors logged?
Is anything happening at all?
Have you tried checking that the scheduler is active?

Hi ​@willhowardnz ,

I’m on PCS. No I havent been using RabbitMQ.

No error while logging in. Yes the scheduler were active.

Hi ​@Harry  - 

I think MSMQ might be your problem then.
 

MSMQ is deprecated from 2025R2 onwards, and completely removed from 26R1 onwards.

If you were relying on MSMQ for your message brokering you need to swap methods.

Thank you ​@willhowardnz. Will go through these and update you.

hi ​@willhowardnz ,

How can I enable push notifications in web.config file as there isnt any line of code in the file. I’m getting a bit confused in the above share topic as it is for business events where’s my issue lies in the automation schedules even from the processing screens too. 😥

@Harry you don't need to add that line. In the 2026 R1 code, EnablePushNotifications defaults to true when the key isn't in web.config, so a missing line means it's on.

Will's question about the scheduler is the one I'd chase. Processing-screen schedules and Trigger by Schedule business events run on the same automation scheduler, so when both stop at once, start there.

Open Automation Schedule Statuses (SM205030) and look for an Initialize Scheduler button. It only appears when the database was restored from a backup taken on another site, and on that site every schedule stays off until someone clicks it. That fits moving to a new instance. Click it only on the site that should be live. If your old 26R1 site is still running, both sites will run the same schedules.

If there's no button, check two things. In 26R2, both schedule screens show a warning while a maintenance lockout is on, and schedules stay suspended until the lockout is ended on Apply Updates (SM203510). Then check web.config. DisableScheduleProcessor in appSettings should be False. When it's True, the scheduler doesn't start on that site.

I checked this against the 2026 R1 code. The 26R2 release notes don't mention either web.config key.