Best practice for Backup → Update → Start workflow?

Questions
1

Hi everyone,

I’m trying to build a simple maintenance workflow with the AMP Scheduler and I’m wondering if I’m missing something.

My goal is:

Take a Backup
↓
Update Application
↓
Update all Store Entries
↓
Start Application

The important part is that I only want the server to start after both update processes have completely finished.

However, what I’m seeing is:

  • Application - Update the application starts the update and the scheduler immediately continues.
  • Store - Update all store entries also starts and the scheduler immediately continues.
  • Application - Start the application is executed while the update(s) are still running in the background.

From what I can tell, the update tasks seem to be asynchronous.

Is there currently any way to wait until these tasks are actually finished?

For example:

  • a scheduler condition
  • a task status variable
  • a “wait until update complete” action
  • or any other recommended approach?

Using a fixed delay (Wait) would work as a workaround, but I’d rather avoid guessing how long updates might take.

I’m running AMP 2.8.0.4.

How are you handling this in your maintenance schedules?

Thanks!