# Execute wizard watcher: Error: input search: Error: Request Timeout after 60000ms
**URL:** https://discuss.elastic.co/t/execute-wizard-watcher-error-input-search-error-request-timeout-after-60000ms/165509
**Category:** Kibana
**Created:** [January 24, 2019, 1:55am UTC](https://discuss.elastic.co/t/execute-wizard-watcher-error-input-search-error-request-timeout-after-60000ms/165509 "2019-01-24T01:55:53Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@aabababba](https://discuss.elastic.co/u/aabababba)
#### Post date: [January 24, 2019, 1:55am UTC](https://discuss.elastic.co/t/execute-wizard-watcher-error-input-search-error-request-timeout-after-60000ms/165509/1 "2019-01-24T01:55:53Z")
# execute wizard watcher: Error: input search: Error: Request Timeout after 60000ms
is it about Server resource consumption is too high?
---
### Author:  [@tsullivan](https://discuss.elastic.co/u/tsullivan)
#### Post date: [January 25, 2019, 12:32am UTC](https://discuss.elastic.co/t/execute-wizard-watcher-error-input-search-error-request-timeout-after-60000ms/165509/2 "2019-01-25T00:32:19Z")
Timeout just means that a request was made, and the time for the response came back exceeded the time the caller wants to wait. Timeouts are important or else you could get something that waits for infinite time
---
### Author:  [@tsullivan](https://discuss.elastic.co/u/tsullivan)
#### Post date: [January 25, 2019, 4:20am UTC](https://discuss.elastic.co/t/execute-wizard-watcher-error-input-search-error-request-timeout-after-60000ms/165509/3 "2019-01-25T04:20:42Z")
Hey sorry, I think I hit Send too early 😃
Timeouts could also be due to other factors like network latency. It kind of depends on if you're seeing this all the time, when you do a certain thing, or randomly. It also depends on what kind of resource you are requesting. I do not know what "execute wizard watcher" means.
If you think it's a server resource issue, then you must be thinking of Elasticsearch performance. If you don't already, get X-Pack Monitoring - it's free with the Basic License.
There are other tools and recommendations you can try to see if resources are an issue:
- Rally: [https://github.com/elastic/rally](https://github.com/elastic/rally) - can test performance in terms of its capabilities, measured by running benchmarking tests.
- Slow Log: [https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-slowlog.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-slowlog.html)
- Query Profiler: [https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-profile.html) - I really recommend this one if you are running another client application against the same Elasticsearch cluster. You can test the queries your application is making to see if they can be improved
---
### Author:  [@aabababba](https://discuss.elastic.co/u/aabababba)
#### Post date: [January 25, 2019, 6:03am UTC](https://discuss.elastic.co/t/execute-wizard-watcher-error-input-search-error-request-timeout-after-60000ms/165509/4 "2019-01-25T06:03:11Z")
thank you ,I go to study about it.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 22, 2019, 6:09am UTC](https://discuss.elastic.co/t/execute-wizard-watcher-error-input-search-error-request-timeout-after-60000ms/165509/5 "2019-02-22T06:09:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.