Main workflow runs even when Trigger Workflow rule is configured to run another sequence

Help Apps
,
1

Hi!

I’m trying to explore UiPath Apps so I created a UiPath project using REFramework for my performer while I have two different dispatchers, each in their own xaml files and are enabled as entry points. In my UiPath Apps, I used the Trigger Workflow rule once the submit button is clicked. The process configured in the Trigger Workflow rule points to the dispatcher (I even overriden the inputs to match with the dispatcher’s needs) but whenever I am trying to test the app, the one that’s running is the Main file (which is the performer) instead of the dispatcher.

How do I fix this? Thank you!

2

It’s really not ideal to have multiple processes branched within one project. You should have the dispatchers as separate automations.

3

yeah, but is that the expected behavior of Trigger Workflow rule? It always runs the main sequence even if it’s set to go to another entry point?

4

I don’t know the answer to that, I just know that you shouldn’t combine processes into one like that.

5

@_pjflo

  1. Did you happen to select the right xaml?
  2. This works best in attended automation if not it might default to the main process which might cause such behaviour

Please check the important note in the link

Cheers