UiPath Apps Start Process not showing input arguments for Agent process

am trying to start an Agent process from UiPath Apps using the Start Process rule on a button click.

The Agent has input arguments defined in Data Manager, for example:

  • requirementId

  • submittedBy

When I run the Agent directly from Orchestrator, these inputs are visible and the job runs successfully when I pass values.

However, when I add the same Agent process in UiPath Apps using Add process, the process is visible, but the Input arguments / Output arguments section is blank. Because of this, I am not able to map App variables to the Agent input arguments in the Input Override section.

I also noticed that normal RPA processes show their input arguments correctly in UiPath Apps, but the Agent process does not.

Hi @Dhruba_Jyoti_Kalita,

Could you please check whether your Agent is deployed as a process in Orchestrator?

If the Agent is not deployed as a process, UiPath Apps may not be able to retrieve its input and output arguments.

Thanks

Deployed. I am able to run Agent through Orchestrator

Hello @Dhruba_Jyoti_Kalita!

I ran into this same scenario on a previous UiPath Apps project just a few months ago. Keep in mind that this was using the traditional UiPath Apps experience, not Studio Web Apps - so things could be different using the new experience.

From what my team observed and found, Agent process arguments do not appear in UiPath Apps the same way normal RPA process arguments do. When adding the Agent process to the app, the process itself may be visible, but the Input / Output Arguments section remained blank.

The workaround we used was to wrap the Agent inside a standard RPA process. The flow would look like this:

UiPath App → Standard RPA Process → Agent Process → Standard RPA Process → UiPath App

So instead of calling the Agent directly from Apps, the App calls a normal RPA process that has the required input and output arguments exposed. For example, the App passes values such as requirementId and submittedBy into the RPA process. Then, inside that RPA process, you call/start the Agent and pass those values into the Agent’s input arguments.

Once the Agent completes, it returns its outputs back to the RPA process. The RPA process can then assign those values to its own output arguments, which are visible and mappable back in UiPath Apps.

Hope this helps! Let me know if you find anything different.