Python Code Loses Indentation When Reopening Workflow

I'm using the Python Code step in Pabbly Connect and I'm running into a formatting issue.

The editor doesn't support indentation with the Tab key because pressing Tab simply moves the focus to the next field. That's inconvenient, but I can work around it by using spaces.

The real problem is that after saving the workflow and reopening it later, all leading spaces at the beginning of indented lines are gone. This completely breaks Python code because indentation is part of the syntax.

Is anyone else experiencing this? Is this a known issue, or is there a recommended workaround to preserve Python indentation?

I'm using the latest version of Zen Browser

Hello Volker,

Thank you for reporting this issue.

Could you please let us know which workflow builder you are using (Old UI or New UI) when experiencing this behavior?

This issue should not occur in the New UI workflow builder, as Python code indentation is generally maintained there even after saving and reopening the workflow.

If possible, please share the workflow URL along with a short screen recording demonstrating the issue. This will help us investigate it further from our end.

We look forward to your response.

Hallo Peeti,

thank you for your fast reply!

I am using the old editor as some apps are missing trggers and actions that seem to only exist in the classic editor.

I attach a screenrecording where you can see it in action:

I open a worklow, execute the python code - everything is working.

I then just add a word to an already existing comment in the code.

Executing again - all indentation is gone.

https://www.youtube.com/watch?v=reZUhoZfuhY

Hello Volker,

Thank you for sharing the video recording.

We were able to reproduce and acknowledge the issue in the Classic (Old UI) workflow builder. It appears that when editing a Python Code step, the indentation may be removed, which can break the code execution.

Please note that we are currently focusing our development efforts on the New UI, as it will be the primary workflow builder going forward. The New UI does not exhibit this indentation issue, and Python code formatting is preserved correctly there.

You mentioned that you are still using the Classic UI because certain apps, triggers, or actions seem to be unavailable in the New UI. Could you please let us know which specific apps, triggers, or actions you are referring to?

As far as we are aware, all applications available in the Classic UI are also available in the New UI. Once you share the details, we'll be happy to verify this and help you, so that you can migrate the workflow to the new UI.

Hallo Preeti,

it's been a while that I checked the new editor. I will start migrating - thank you for your support!

Volker

Hello Volker,

We're glad to know that the information was helpful and that you will be migrating to the New UI.

Since we have addressed your concern, we will now be closing this thread. Should you have any questions or require any assistance in the future, please don't hesitate to reach out to us. We'll be happy to help.