GCode inconsistently processed out of order

[morphias2004]

Describe the bug

GCode in customs actions are not always processed in order.

To Reproduce

1. Create a custom action with multiple GCode commands
2. Save the custom action
3. Execute the custom action

When the button for the custom action is pressed, the GCode is sometimes sent out of order.

Generally caused when using different custom actions in different orders.

Expected behavior

For the GCode to be processed in the order it is typed into the custom action.

Screenshots

I have a Prusa XL 5 tool head. I have custom actions created to pick up tool X and bring it to the front center. This allows me to inspect the nozzle and clean it if required, etc.

I also have custom actions to park the current tool and also one to bring the current tool to the front center.

If I run a Park, then a Grab Tool 1, then a Grab Tool 3, etc; it will inconsistently process the commands out of order.

For example:

• the move to the front center, then get the tool, then home XY

then

• home XY, then get the tool and then move to the center

This is an example of the terminal output from hitting Grab Tool 1, which result in the tool pickup and move being out of order.

then hitting Grab Tool 3, but this time the tool pick-up and move happen in the correct order

then hitting Grab Tool 5, and again it does it out of order

then telling it to Grab Tool 2 and it does it in a completely different order

It's so random.

General Information:

• RPi 4 4GB
• Brand new install of OctoPi 1.0.0

• OctoDash Version 2.3.1
• OctoPrint Version 1.10.1