can i define the order of automations running?

Dezi

hello

can I define the order of automations running?

Ray Lindstrom

Hi @Dezi

Many have asked this question. I've seen posts with contradictory reports. If the proper answer has been provided, I'm unable to isolate it amongst all of the varying answers.

One user claims the most recently saved automation will run first. Another user claims the opposite in that the most recently saved automation will run last.

I haven't been able to find anything from Smartsheet that specifies what the true order is, or if there's any way at all for a user to force any desired order.

My opinion is that this is a question for the Smartsheet team more than the community.

@Maxwell Griffith @Alison Clancy @Arsineh, Would it be possible to get some help finding out the answer to this?

Colleen Patterson

@Ray Lindstrom @Dezi

My experience does not match with the most recently created automation running first, and they seem to not have any order in the manner in which they run. Would also love to see some additional clarification here.

In order to get around this, and have some control over when things are triggered, I have modified my Run When criteria to be offset times, which created the sequential effect.

Bosakie

In my experience I use a status field. When the status field changes the appropriate automation will take place. Example: I have a status filed for Development; this is used for when a new project is created in the development column. I have a notice going out to the Developer and an heads up message to IT Security that a project will need a security scan. It will go through Unit testing and then to a queue column for QA Testing. At that time, when the project status changes to QA Testing another automation goes out to the QA team to schedule the testing and the process continues with the appropriate automation. Now couple this with the Timeline function and you can see at a glance where in the process the project is and the time frame for each column. I have a start/end dates that can change for each column header so it accurately displays the length of time it should take for the column it is in. Sure cleaned up the issues between Developers and the QA team and encourages communications. I also implemented a weekly stand up for 30 minutes to go over the project in the pipeline.