> 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/searching-applications-folder-with-execution-id-times-out.md).

# Searching Applications folder with Execution ID times out

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

When calling `**/applications/{application_name}/executions/search with an execution_id**`,\*\* \*\*the calls time out for some pipelines. This time out error makes it difficult to find specific executions as needed. Example Search Query

```
curl --location --request GET 'http://{spinnaker-gate}/applications/{application_name}/executions/search?eventId={some_uuid}' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'Cache-Control: no-cache' \
--header 'Authorization: Basic {token}' \
--header 'Cookie: SESSION={session_id}'
```

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

The number of executions for the queried pipeline can grow so large that it can reach the default timeout limit and return a failure. This is expected behavior for a scaled up Spinnaker that has had many pipelines put through it.