Hi everyone, I’m trying to create a RPA workflow with an agent. In the earlier versions, the “Run Job” block would easily run my agent. I think a recent update has changed it to “Run agent” automatically. When i try to map the input variables, the data mapper table is blank. Has anyone else encountered this?? And is there a workaround present?
yes, this can happen after the recent update where Run Job is changed to Run Agent. If the Data Mapper table is blank, try refreshing/reopening the workflow and checking that the agent’s input arguments are properly defined and published.
As a workaround, you can try deleting and re-adding the Run Agent activity, then remap the inputs. This usually refreshes the available input variables.
Hi @_MITRA_DIVYANSH ,
The blank Data Mapper is usually caused by the Run Agent activity not loading the agent’s input schema correctly. Republishing the agent and re-adding the activity is often the quickest fix. If it persists, collect logs and raise a UiPath support ticket, as it may be a product regression.
Thanks
Hi @_MITRA_DIVYANSH,
This is an expected behavior, not a bug specific to you. Since UiPath.System.Activities 25.4.2, “Run Agent” was permanently merged into the Run Job activity; searching for “Run Agent” now just inserts Run Job automatically.
In the Input field, click Refresh arguments, the mapper often loads empty until you force a refresh of the process’s argument list. If it’s still blank, republish the agent and redeploy/upgrade the corresponding process in the Orchestrator folder. A stale process version is the most common cause of a missing argument list.
If the above doesn’t fix then, update Studio to 2025.0.161 or later. Versions before that use the older Expression Editor instead of the Data Mapping table, so an outdated Studio build can show an empty/non-functional mapper.
If none of that works, you can bypass the mapper and set inputs directly via VB/C# expression, e.g.: New Email_Rewriter_Input() With {.feedback = "sample feedback", .originalEmail = "sample email content"}
Refer the below documentation.
I hope this helps.
Cheers!
I’ve seen similar behavior when the Agent arguments are not refreshed correctly in the Run Job activity.
Make sure the values created in the Agent’s Data Manager are Input Arguments, not normal/local variables.
After adding/changing the arguments, publish the Agent again and update/redeploy the Agent process in Orchestrator. The workflow reads the argument schema from the deployed process.
In the RPA workflow, reselect the Agent process in Run Job, then click Refresh arguments beside the Input field. This should reload the arguments into the Data Mapper.
Also check the UiPath.System.Activities package version. There have been fixes specifically around Run Job input arguments/Data Mapper not refreshing correctly, so I would update the package if you are on an older version.
Please let me know if it works
I ran into the exact same issue. What’s strange is that the same workflow was working fine just a week ago. I suspect a recent update broke the argument communication between the RPA workflow and the Agent. If you figure it out, please let me know the solution!
I’ve seen this happen when the agent input schema is not being refreshed correctly in the Run Agent activity.
I would first open the agent and make sure the required input arguments are defined and saved. Then refresh/reopen the workflow and try adding the Run Agent activity again.
If the Data Mapper is still blank, try removing and re-adding the Run Agent activity, and make sure the agent is published/saved with the latest version.
If it still doesn’t show the inputs, it could be related to the recent change from Run Job to Run Agent. In that case, sharing a screenshot of the agent’s input definitions and the blank Data Mapper would help identify whether it’s a configuration issue or a product/version issue.
Just to add to the discussion “Run Agent” isn’t really a separate activity in latest UiPath activities package. From package v25.4.2 onwards, it hs been replaced by Run Job. If you search “Run Agent” in Studio, it still shows up, but it actually adds the Run Job activity. So that “auto-switch” some of you saw is expected, not a bug.
Also, one thing people often miss: an argument only shows up in the Data Mapper if it’s actually used in the agent’s prompt using the @ picker. If you added an argument in Data Manager but never referenced it with @ in the prompt, it won’t show up as input later.
Check the below points:
- Open the agent, check the argument is under Data Manager > Input tab
- Make sure it’s referenced in the prompt using @
- Republish the agent
- Redeploy the process in Orchestrator
- Back in Studio, reselect the process in Run Job and hit “Refresh arguments”
- Still blank? Delete the Run Job activity and add it fresh
- Also check your UiPath.System.Activities package version - update if it’s old, there were some fixes around this