Skip to main content
Solved

Automation Schedule suddenly stop working

  • September 18, 2023
  • 8 replies
  • 497 views

Hi everyone,

Does anyone here encountered their automation schedule suddenly stopped processing after a few days? We have the following configured to automate recognition of deferred taxes. 

It is running but nothing is processed. Any advise? Tried replicating this same configuration on my local instance but gives the same result.

 

Thanks,

 

Best answer by madeborahdelfin56

@apallawala21 

I have this raised with the Acumatica support team and they told me that this is a known issue. I do not know if locking the system has an impact because we have deployed a number of customizations before this issue appeared. As far as I remember this happened after the system was upgraded. 

8 replies

dcomerford
Captain II
Forum|alt.badge.img+16
  • Captain II
  • September 18, 2023

Can you check the Status on the Automation Schedule Status and whether it is initialized

 


Yes, it is initialized. i also inspected its history and there were logs per every minute. 


dcomerford
Captain II
Forum|alt.badge.img+16
  • Captain II
  • September 18, 2023

Dont know to be honest i presume if you do it manually on the screen it gives you a result and the conditions are the same as running it manually


Kandy Beatty
Captain II
Forum|alt.badge.img+18
  • Captain II
  • September 18, 2023

HI @madeborahdelfin56 

What is the schedule on the Automation Schedule?

Also, have you tried to make it inactive then activate it again?


Hi Kandybeatty49,

I did not deactivate it. I deleted it and created a new automation with the same conditions and filters.


Forum|alt.badge.img
  • Jr Varsity II
  • April 14, 2025

Changing the next execution time and deactivating/reactivating helped.


Forum|alt.badge.img
  • Jr Varsity II
  • January 6, 2026

@madeborahdelfin56 

Have you locked the system for any reason and then faced the issue or has it happen event without locking the system?

 


@apallawala21 

I have this raised with the Acumatica support team and they told me that this is a known issue. I do not know if locking the system has an impact because we have deployed a number of customizations before this issue appeared. As far as I remember this happened after the system was upgraded.