> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/agent-deployment-error-exceptions-operationtimedoutexception-timeout-exceeded-for-operation.md).

# Agent Deployment Error- exceptions.OperationTimedOutException- Timeout exceeded for operation

### Issue <a href="#issue" id="issue"></a>

When using Agent, customers may experience that they see the following errors during a deployment execution:

```
message="com.netflix.spinnaker.clouddriver.exceptions.OperationTimedOutException: Timeout exceeded for operation ......., type: 6, account: .....-ingress-dev, time: 30022 ms, timeout: 30000 ms
 at io.armory.kubesvc.services.ops.KubesvcOperations.performOperation(KubesvcOperations.java:96)
 at io.armory.kubesvc.services.ops.cluster.ClusteredKubesvcOperations.performOperation(ClusteredKubesvcOperations.java:70)
 at io.armory.kubesvc.util.OperationUtils.perform(OperationUtils.java:76)
 at io.armory.kubesvc.services.ops.executor.KubesvcExecutor.deploy(KubesvcExecutor.java:301)
 at jdk.internal.reflect.GeneratedMethodAccessor703.invoke(Unknown Source)
 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
```

### Cause <a href="#cause" id="cause"></a>

The error indicates that the Clouddriver sent a `deploy operation` to the kubesvc Agent and was not able to obtain the result back from the Agent in time.