You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the Solr index example it times out after 175 seconds. This is fine except no sign of an error is displayed to the user unless watching workflows with Terminus, which we can't reasonably expect folks to do. It would be great if we could surface an error operations in Quicksilver hooks time out. In this case the Solr index operation takes about 20 minutes.
terminus workflow:watch solr-power
[notice] Watching workflows...
[notice] Finished workflow c554cc42-0985-11e7-8ce6-bc764e1141f9 Create a Multidev environment () at 2017-03-15 13:51:22
[notice] ------ Operation: Index Solr Power items after multidev creation finished in 175s (slow-query) ------
Operation exceeded maximum execution time of 120 seconds.
The text was updated successfully, but these errors were encountered:
I know this is old, but for future searchers, the only way I've found to address this is to increase the maximum_execution_time as described here: https://pantheon.io/docs/timeouts
It's not a great solution, but it's the only one that I know of.
Using the Solr index example it times out after 175 seconds. This is fine except no sign of an error is displayed to the user unless watching workflows with Terminus, which we can't reasonably expect folks to do. It would be great if we could surface an error operations in Quicksilver hooks time out. In this case the Solr index operation takes about 20 minutes.
The text was updated successfully, but these errors were encountered: