# Not allowed to increase reporting capture timeouts in Elastic cloud **URL:** \ **Category:** Kibana\ **Created:** [May 28, 2020, 9:05am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697 "2020-05-28T09:05:28Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Martijn04](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martijn04/32/45572_2.png) [@Martijn04](https://discuss.elastic.co/u/Martijn04)\ **Post date:** [May 28, 2020, 9:05am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/1 "2020-05-28T09:05:28Z")
Hello, We are using the Elastic Cloud service. When generating a report I get the following error message: An error occurred when trying to open the Kibana URL. You may need to increase 'xpack.reporting.capture.timeouts.openUrl'. TimeoutError: waiting for selector ".application" failed: timeout 30000ms exceeded In the deployment page \> edit \> Kibana \> User settings overrides I tried to increase the value in: xpack.reporting.capture.timeouts.openUrl: 60000 It gives the following message: 'xpack.reporting.capture.timeouts.openUrl': is not allowed Is there another way to increase this timeout? ---
**Author:** ![111317](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/111317/32/66249_2.png) [@111317](https://discuss.elastic.co/u/111317)\ **Post date:** [June 1, 2020, 12:14am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/2 "2020-06-01T00:14:29Z")
This issue is documented at [https://www.elastic.co/guide/en/cloud/current/ec-manage-kibana-settings.html](https://www.elastic.co/guide/en/cloud/current/ec-manage-kibana-settings.html). Just change the value of xpack.reporting.queue.timeout. The default value is 30000 (30 seconds). ---
**Author:** ![bobonacus](https://avatars.discourse-cdn.com/v4/letter/b/e56c9b/32.png) [@bobonacus](https://discuss.elastic.co/u/bobonacus)\ **Post date:** [June 1, 2020, 11:16am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/3 "2020-06-01T11:16:00Z")
I have changed `xpack.reporting.queue.timeout: 600000` and now get this error : You may need to increase 'xpack.reporting.capture.timeouts.openUrl'. TimeoutError: waiting for selector ".application" failed: timeout 30000ms exceeded If I try and change that `xpack.reporting.capture.timeouts.openUrl: 600000` it says 'xpack.reporting.capture.timeouts.openUrl': is not allowed ---
**Author:** ![Martijn04](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martijn04/32/45572_2.png) [@Martijn04](https://discuss.elastic.co/u/Martijn04)\ **Post date:** [June 2, 2020, 3:12pm UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/4 "2020-06-02T15:12:44Z")
I also tried to increase the xpack.reporting.queue.timeout but the issue remained the same ---
**Author:** ![Matt\_Wisner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matt_wisner/32/71317_2.png) [@Matt\_Wisner](https://discuss.elastic.co/u/Matt_Wisner)\ **Post date:** [June 29, 2020, 7:14pm UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/5 "2020-06-29T19:14:33Z")
Same issue for me. I have tried increasing xpack.reporting.queue.timeout to really high numbers, and even tried to increase the size of the Kibana instance. I keep getting `You may need to increase 'xpack.reporting.capture.timeouts.openUrl'. TimeoutError: waiting for selector ".application" failed: timeout 30000ms exceeded` ---
**Author:** ![mhelastic](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@mhelastic](https://discuss.elastic.co/u/mhelastic)\ **Post date:** [July 3, 2020, 11:04am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/6 "2020-07-03T11:04:46Z")
> [@bobonacus](#): > > xpack.reporting.queue.timeout: 600000 We are facing with the same problem as well ---
**Author:** ![bobonacus](https://avatars.discourse-cdn.com/v4/letter/b/e56c9b/32.png) [@bobonacus](https://discuss.elastic.co/u/bobonacus)\ **Post date:** [July 3, 2020, 11:23am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/7 "2020-07-03T11:23:11Z")
After lots of different options tried through ES support the only solution that worked was to up the RAM for the kibana instance ---
**Author:** ![mhelastic](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@mhelastic](https://discuss.elastic.co/u/mhelastic)\ **Post date:** [July 3, 2020, 12:40pm UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/8 "2020-07-03T12:40:39Z")
Hi Robert, I tried upgrading the RAM as well to 2GB's, and the screenshots now are changed to: ![elastic2](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c5ed0aa50ea80c577cbbcb3d166b63c3e69a5e4e.png) How many GB's of RAM did you add? We barely use Kibana. Maximum one concurrent user. ---
**Author:** ![bobonacus](https://avatars.discourse-cdn.com/v4/letter/b/e56c9b/32.png) [@bobonacus](https://discuss.elastic.co/u/bobonacus)\ **Post date:** [July 3, 2020, 1:02pm UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/9 "2020-07-03T13:02:37Z")
I had to go from 1 to 4GB which isn't the best given the increase in cost ☹ ---
**Author:** ![mhelastic](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@mhelastic](https://discuss.elastic.co/u/mhelastic)\ **Post date:** [July 3, 2020, 1:27pm UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/10 "2020-07-03T13:27:09Z")
Hi Robert, Thanks for the additional info. I have have upgraded to 4 GB's as well and then it seems to work. We regret that this is necessary, because before we upgraded to version 7.7 it has always worked well. Hopefully Elastic will find a fix so we can downgrade back to 1 GB. Cheers ---
**Author:** ![sfenman](https://avatars.discourse-cdn.com/v4/letter/s/f04885/32.png) [@sfenman](https://discuss.elastic.co/u/sfenman)\ **Post date:** [July 6, 2020, 10:39am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/11 "2020-07-06T10:39:12Z")
Any other solutions to this? I can't even export a small visualization as a pdf because of this error. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 3, 2020, 10:39am UTC](https://discuss.elastic.co/t/not-allowed-to-increase-reporting-capture-timeouts-in-elastic-cloud/234697/12 "2020-08-03T10:39:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.