Skip to main content
Solved

Kicking off Automation after one completes

  • October 22, 2024
  • 4 replies
  • 35 views

Hello, 

We have two Automation schedules for a custom Delinquency Process. Our first Process is a customer Block stage and the second is a Customer Warning stage.

We want to schedule these to run nightly and the 2nd process should only start after the 1st automation schedule completes

What is the best way to accomplish this without combining them to one?

 

 

Best answer by craig2

Just from experience, most processes in Acumatica should take less than 30 minutes, so spacing the schedules in that way should provide a decent level of assurance that there won’t be overlap.  If something takes longer than that to run, you should reevaluate the server size for your instance.

But, that is all hypothetical, and you are correct, spacing the schedules is a passive solution.  If you want a more concrete “Run B when A is complete,” you could possibly leverage the AUSchedule.LastRunDate or, if it’s triggering an Import Scenario, SYMappingActive.CompletedOn in a GI, filter for when “Import A completes Today,” then use that to trigger a Business Event that in turn drives Import B. 

That’s a lot more moving parts and Business Events can get a little fussy if you throw too much at them, but it may work more like you expect.

Good luck!

View original
Did this topic help you find an answer to your question?

4 replies

craig2
Pro I
Forum|alt.badge.img+3
  • Pro I
  • 97 replies
  • October 22, 2024

Hi @bezzo16 ,

Just an idea, would it be possible to just space the schedules far enough apart to ensure the first is completed?  So 11:30PM and 12:00AM, perhaps?


dcomerford
Captain II
Forum|alt.badge.img+15
  • Captain II
  • 635 replies
  • October 22, 2024

Agree with @craig2 would suggest you also tick the exact time so they dont move

 


  • Author
  • Freshman I
  • 1 reply
  • October 22, 2024

@craig2  @dcomerford  We only want the second process to start when the first has finished scheduling at exact time you could risk the second process starting while the first has not finished?


craig2
Pro I
Forum|alt.badge.img+3
  • Pro I
  • 97 replies
  • Answer
  • October 22, 2024

Just from experience, most processes in Acumatica should take less than 30 minutes, so spacing the schedules in that way should provide a decent level of assurance that there won’t be overlap.  If something takes longer than that to run, you should reevaluate the server size for your instance.

But, that is all hypothetical, and you are correct, spacing the schedules is a passive solution.  If you want a more concrete “Run B when A is complete,” you could possibly leverage the AUSchedule.LastRunDate or, if it’s triggering an Import Scenario, SYMappingActive.CompletedOn in a GI, filter for when “Import A completes Today,” then use that to trigger a Business Event that in turn drives Import B. 

That’s a lot more moving parts and Business Events can get a little fussy if you throw too much at them, but it may work more like you expect.

Good luck!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings