# Excecute runs in sequential order **URL:** \ **Category:** General\ **Created:** [February 8, 2023, 5:37pm UTC](https://guildai.org/t/excecute-runs-in-sequential-order/992 "2023-02-08T17:37:31Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![bbach63](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@bbach63](https://guildai.org/u/bbach63)\ **Post date:** [February 8, 2023, 5:37pm UTC](https://guildai.org/t/excecute-runs-in-sequential-order/992/1 "2023-02-08T17:37:31Z")
I would like to prevent all runs in a grid search running in parallel. The only way I found is to use staged runs and the queue option for a sequential execution with `wait-for-running=yes`. 1. Is there another way to achieve that goal? 2. Does the queue option only work with GPUs? I get an error as if guildai cannot find a tensorflow version, though the “non-staged” run works perfectly. ---
**Author:** ![garrett](https://yyz1.discourse-cdn.com/flex031/user_avatar/guildai.org/garrett/32/224_2.png) [@garrett](https://guildai.org/u/garrett)\ **Post date:** [February 24, 2023, 4:43pm UTC](https://guildai.org/t/excecute-runs-in-sequential-order/992/2 "2023-02-24T16:43:00Z")
Guild only ever runs operations in series. The only way to run operations in parallel is to use queues (or otherwise start Guild commands independently, e.g. separate terminals, background jobs, etc.) What are you seeing where Guild runs operations in parallel? ---
**Author:** ![bbach63](https://avatars.discourse-cdn.com/v4/letter/b/b9bd4f/32.png) [@bbach63](https://guildai.org/u/bbach63)\ **Post date:** [March 25, 2023, 11:00am UTC](https://guildai.org/t/excecute-runs-in-sequential-order/992/3 "2023-03-25T11:00:16Z")
I was using the R package for guildai. I realized that I had an outer loop somewhere that caused guild\_run to start mulitple sessions. I could fix the issue: Guild is running as you described. Thank you.