# Change in how Action sequences run **URL:** \ **Category:** Ask for Help\ **Created:** [January 30, 2024, 3:50pm UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264 "2024-01-30T15:50:12Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 30, 2024, 3:50pm UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264/1 "2024-01-30T15:50:12Z")
I migrated my app from Classic to Apps. Doing the final test before some demos and I discovered a change in how action sequences work. This sequence used to worked fine - now it doesn’t. I have an action sequence that does a handful of set-col-cals / add rows. One set-col-val is for a row that might not exist (sometimes it exists…sometimes it doesn’t depending on where this operation started). The sequence used to ignore this failure and continue processing - now it aborts without finishing the flow. I never quite knew how AS flowed (timing, handling of errors, etc.) but I do know this used to work and now it doesn’t. It seems now that if any one action fails in the Action sequence it aborts the rest of the sequence. Any insights from the experts? ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [January 30, 2024, 3:55pm UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264/2 "2024-01-30T15:55:33Z")
> [@MattLB](#): > > The sequence used to ignore this failure and continue processing - now it aborts without finishing the flow. > > I never quite knew how AS flowed (timing, handling of errors, etc.) but I do know this used to work and now it doesn’t. It seems now that if any one action fails in the Action sequence it aborts the rest of the sequence. As far as I’m aware, it’s always worked this way 🤷‍♂️ So I’m a bit surprised to see you say that it worked as you described in Classic Apps. Maybe I’m wrong… In the not-too-distant future, I expect we might have a nice elegant way to handle this, but in the meantime you might need to create two conditional branches - one with the set column values and one without. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 30, 2024, 4:10pm UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264/3 "2024-01-30T16:10:49Z")
Behavior changed - that’s all I got. And yes - the benefit of new Glide is I can use the Action library to easily duplicate, change and load the alternative method. The good news is I know when the sequence occurs so I can create and deploy the altered path. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 30, 2024, 4:35pm UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264/4 "2024-01-30T16:35:46Z")
Just a comment on Classic v Apps. In Classic if I needed to make this change I would have to find the places were I used this sequence by scouring the app and update each one by hand. And hope I didn’t miss one (this sequence is used in a handful of different places) With Apps I went to the Action library, duplicated sequence, changed its name and modified the sequence, then use ‘find use’ to replace incorrect sequences and boom - done. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [January 31, 2024, 12:19am UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264/5 "2024-01-31T00:19:59Z")
> [@Darren\_Murphy](#): > > As far as I’m aware, it’s always worked this way 🤷‍♂️ I have been on Classic since the very first days and I think it always worked that way. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 31, 2024, 12:50am UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264/6 "2024-01-31T00:50:31Z")
Hmmmm…I think it is similar to what @Jeff_Hager noted in his Hard Stops missive (e.g. Glide stops processing a sequence, which it didn’t do in Classic). [My Hard Stops and Annoyances](https://community.glideapps.com/t/my-hard-stops-and-annoyances/66846) > [@My Hard Stops and Annoyances](https://community.glideapps.com/t/my-hard-stops-and-annoyances/66846/1): > > I perform some actions through a Single Relation, such as a Set Column Action. This action is among other actions in a custom action that sets some values in the current row as well at rows in other tables before executing a Show Detail Screen action. I noticed that the button completely disappears if one of the single relations are empty. If there are no matches in the relations, then there is nothing that to needs to be set, but there is no reason why the rest of the action sequence can’t continue to run. I still need those other actions to occur but the button completely disappears. Short of breaking a single IF branch in the custom action into 3 or 4 separate branches to account for every possible scenario, I see no reason why the entire button needs to be disabled. This was not an issue in classic apps. I did the same thing and the button still worked as expected. This is only an issue introduced with New Apps. > Notice the highlighted actions. The relations for those actions may or may not be empty. If they are empty, who cares…the rest of the action sequence should work, so there is no reason to hide the button that calls this custom action. I’ll have to add 3 extra branches just to account for the times that one or both of the relations are empty and duplicate a lot of logic. > ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/4/74c4dad8e5a35bb87c72e499c9420a4cbb95f015.png) In any case - found a work around/fix. ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [February 7, 2024, 12:50am UTC](https://community.glideapps.com/t/change-in-how-action-sequences-run/70264/7 "2024-02-07T00:50:50Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.