Forum Archive

I am working on a side project that uses a modular workflow ( WF ) approach.

The main WF calls a sub WF, which contains a Python script, and afterwards uses its own Python logic to further enhance the output.

Running the main WF crashes / freezes Editorial every second time. Replacing the Python script in the main WF with Editorials Action logic runs flawlessly as expected. The only downside for this approach is the rather long chain of actions.

It looks like Editorial can handle only one ( or maybe more? ) Python script on the same "execution level" at a time.

Is this issue known ( to anyone ) and does someone have a possible solution for it?

@Stefano Could you please give us some steps to replicate the behavior that you are seeing?

I made a workflow a while ago called modular Python. Maybe this is what you are trying to achieve? Not really sure what you are asking.

http://www.editorial-workflows.com/workflow/5284439445733376/azjk271i9uw

Thanks to both of you @ccc and @TutorialDoctor for your replies.

@ccc : I have set up a simplified version of my modular approach and it works without flaws. There must be something else going on. I will investigate and keep you int the loop.

@TutorialDoctor : I have downloaded your WF — interesting approach! Here comes my way:

-- Main WF : defines some ( action ) variables, calls a first Sub WF, which mainly consists of a Python script for producing an out- / input. A second Sub WF ( again a Python script ) is run to construct the final result.

The reason for my approach: I can use the first Sub WF to build some other main WFs. All future bug fixes and enhancements in the WF module will immediately reflect in any Main WFs using it. Nice! No tedious copying etc.

Okay, so you want to be able to pass data between workflows?

I created a main workflow with a Set Variable with a value of 2 and Sub-Workflow action that calls another workflow underneath that.

In that second workflow I created a Run Python Script action that has the following code:

import workflow
print(workflow.get_input())

When I run the first workflow, 2 is printed to the console.

Is this the type of setup you want?

That is exactly one setup I have @TutorialDoctor :

1. Main WF calls the ( modular ) Sub WF and processes the output with actions. Works fine.

2. Main WF calls the ( modular ) Sub WF and processes the output by calling a Python script — I have moved the previous second Sub WF one level up. Here Editorial crashes at every second Run of the Main WF. After killing Editorial the first run is fine again and ... crashes afterwards. Puzzling.

Maybe Editorial doesn't like to process Python in different WFs during one combined run?

@omz, any idea / explanation form your side?