Why does the Run Job activity show unknown types, unresolved arguments, or missing input/output bindings after an Agent is updated or deployed in Orchestrator?
Issue Description
When an Agent process is updated in Orchestrator — including changes to its input/output argument schema — UiPath Studio does not automatically refresh the local schema definition for the Run Job activity. As a result, the Run Job activity in the calling workflow displays unknown types, unresolved input/output arguments, or fails to render correctly at design time, even though the underlying packages are intact and the project works in other environments.
The issue is specific to the local machine where the project-level cache (.local folder) holds a stale copy of the Agent schema. Standard troubleshooting steps such as package reinstall and cache clearing do not resolve it.
Resolution
Step 1 — Delete the Project-Level Cache
- Close UiPath Studio completely.
- Navigate to the project folder on the local machine.
- Enable hidden files in Windows Explorer: View → Show → Hidden items
- Locate the .local folder inside the project directory.
- Back up the .local folder to a safe location/folder.
- Delete the original .local folder.
- Reopen the project in UiPath Studio.
Step 2 — Manually Refresh Run Job Activity Arguments
- Open the workflow containing the Run Job activity.
- Re-select the input and output arguments in the Run Job activity to force a schema refresh.
- Re-validate all activity bindings in the workflow.
- Run in Debug mode to confirm the activity resolves correctly.