Automation cloud - Agent Process

Help Automation Cloud
, ,
1

Hello team, we are facing some Challenges when we are running the agent process from Desktop studio which was worked find without any blocker/Issue

Issue : UiPath Agent Error: Failed Dependency | Error Code: 424

Error Code - 424 from cloud studio
Error Code - 424 from cloud studio942×376 108 KB

Error Code - 424 from desktop studio
Error Code - 424 from desktop studio862×177 36.7 KB

Can someone share the details if you came across similar error

2

Hi bro, we haven’t faced this exact issue before, but Error 424 (Failed Dependency) usually indicates that one of the dependencies required by the Agent isn’t available or responding correctly. Since the process is running fine from Studio, it might be worth checking the Agent runtime configuration, package dependencies, Orchestrator connectivity, or any services/APIs being called during execution. Could you also share the Agent version and recent logs for further investigation?

3

Hi @nandhagopal.perumal ,
Agent process cannot access or connect to a required dependency during execution. This can be due to missing package dependencies, Agent service issues, network/connectivity restrictions, expired authentication tokens, or an environment mismatch between Agent Builder and Desktop Studio.

Troubleshooting steps:

  • Verify all project dependencies/packages are installed and updated.
  • Rebuild and republish the Agent project.
  • Sign out and sign back into UiPath Studio/Assistant.
  • Check internet connectivity and firewall/proxy settings.
  • Clear local package cache and restart UiPath services.
  • Review Studio and Agent execution logs for the specific dependency that failed.
  • Ensure the Robot, Studio, and Agent versions are compatible.

Thanks

4

Hi @nandhagopal.perumal

Hi, the error seems to be related to the Run Agent activity. Please try using Run Job instead, and make sure the Agent is published and updated in Orchestrator. Also check if the same Agent runs successfully directly from Orchestrator.

5

Hi @nandhagopal.perumal,

Check the trace logs of the run first. Open Orchestrator → Agentic Processes → open this run → Traces tab (or the Execution Trace panel you already have open and expand the LLM call / tool-call node under “Agent run - Agent” instead of reading only the top summary). It’ll show which specific dependency returned the failure and its real status code.

Since it worked before and now doesn’t, check what changed recently:

  • Integration Service connections used by any Tool in this agent, OAuth tokens expire silently and this is the single most common cause of a 424 wrapping a downstream auth failure.
  • LLM model deployment/connection, verify the model used by the agent is still active, not rate-limited, not deprecated/retired on the provider side.
  • Context Grounding index, if the agent uses RAG, confirm the index still exists and wasn’t rebuilt/deleted.
  • Agentic Automation license/feature entitlement on the tenant, a separate known error (AGENT_RUNTIME.LICENSE_NOT_AVAILABLE, HTTP 403) exists for license exhaustion, so if it’s 424 specifically, it’s pointing at a tool/API dependency, not licensing.
  • Package/version drift, confirm the Agent process version pinned in your “Run Agent” activity in Desktop Studio still matches what’s published/live in Orchestrator.

Thanks!

6

The automation executes successfully in UiPath Studio; however, an error occurs when the same process is triggered through the Agent Runtime. This behavior suggests that the runtime environment is unable to fulfill one or more execution prerequisites. Potential factors include unavailable services, configuration inconsistencies, connectivity limitations, authorization issues, unsupported package versions, or differences between the Agent and Studio execution environments.

Recommended Actions:

  • Confirm that all required activity packages and project references are available and on supported versions.
  • Publish a fresh build of the project and redeploy the latest package.
  • Refresh UiPath authentication by re-logging into Studio and Assistant.
  • Verify that network policies, firewall rules, and proxy configurations are not blocking runtime communications.
  • Validate access to all required assets, credentials, connections, and external services.
  • Restart UiPath services and clear cached package data to eliminate locally stored issues.
  • Review Agent Runtime, Robot, and Studio logs to identify the exact component or service causing the failure.
  • Ensure consistency across Studio, Robot, Assistant, and Agent Runtime versions.
  • If the workflow includes AI or LLM activities, confirm that the configured endpoints, permissions, and authentication settings are valid and accessible.
7

Hi @nandhagopal.perumal

welcome to the UiPath Community! :waving_hand:

The Error Code 424 (Failed Dependency) generally indicates that a dependency required by the Agent Process is unavailable or failing during execution. Since the process was working previously, I would recommend checking the following:

  • Verify that all required dependencies/packages and connections are available in the Automation Cloud environment.
  • Check whether the Agent, model, or required resources used by the process are deployed and accessible.
  • Review the execution logs and download the detailed logs to identify the actual dependency that is failing.
  • Verify that you are using the correct tenant and environment and that the required permissions are available.
  • If the issue started recently without any process changes, try republishing/redeploying the solution and running it again.

Since the error appears in both Studio Web/Cloud and Desktop Studio, the detailed execution logs may provide the best clue about which dependency is failing. If possible, please share the complete error message or logs (after removing any sensitive information).

Hope this helps! :blush::rocket:

8

Hi,

Error 424 – Failed Dependency generally indicates that the Agent Process is unable to access or initialize one of its required dependencies.

Since the process was working previously, I would suggest checking:

  1. Agent Process dependencies and referenced resources.

  2. Package/dependency versions in Desktop Studio.

  3. Connections and authentication used by the Agent.

  4. Required permissions for the user/robot.

  5. Any recent changes or updates in Automation Cloud or UiPath Studio.

  6. Whether the same Agent Process works after refreshing/re-publishing the latest version.

If possible, please also check the detailed execution logs/trace logs, as they may identify the exact dependency that is failing.

Hope this helps.