Jump to content

Recommended Posts

Posted

Hello Rulex Community,

Why even though I added the task Runtime Variables at the top level the flow doesn't work correctly and it seems that the flow's variables don’t assume the right values (even though extracting the module makes it work correctly)?

Thanks

Posted

Hi, 

To make sure that the module is executed after the Runtime Variables task I would suggest you to add the Select Flow task that works as a kind of traffic light preventing the computation from continuing if all the tasks before it are not computed.

Before:

spacer.png

After:

spacer.png

Flow computation will proceed only when both inputs (both the Data Manager and the Runtime Variables task) are correctly computed, so we can be sure that the Execute Rulex Flow File task is always executed next. Be sure to update the mapping in the Execute Rulex Flow File task, and define the input type in the Select Flow task.


Another solution could be exploiting priorities. If you right-click you can edit the priority on each task. Tasks with a higher priority value will be computed first. For example you can do this:

spacer.png

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...