This commit is contained in:
2021-12-23 20:16:06 +00:00
parent a22e1bcd72
commit 593dcb576b

View File

@@ -823,12 +823,12 @@ BUILD 8.0.0-beta.0.6 CHANGES OF NOTE
- Changed how AYANOVA_REPORT_RENDERING_TIMEOUT setting is used and interpreted
- setting is now in minutes not milliseconds
- docs updated to reflect how it works
- this setting is now an overall timeout for the entire report rendering process, will stop any processing if it goes over this limit see docs for more info
- this setting is now an overall timeout for the entire report rendering process, will stop any processing if it goes over this limit and return an error to the user, see docs for more info
- New automatic server job added that checks every 5 minutes for stuck report rendering processes (ones that went over the AYANOVA_REPORT_RENDERING_TIMEOUT setting) and terminates them
- changed display message and help link at web app end for when a timeout happens
- Default settings for time out are a best guess by me and we should figure this out as we run into it until we have a sane default for most people.
For now I'm defaulting to 3 minutes total for an entire report generation and hard caps of no less than 1 minute and no more than 15 minutes no matter the setting people use
Let me know if 3 minutes is not a high enough default or 15 is not max enough for any normal usage you anticipate
- changed display message and help link at web app end for when a timeout happens with clear docs on what to do
- Default settings for time out are a best guess by me and we should figure this out as we run into it until we have a sane default for most people as the ultimate release value.
For now I'm defaulting to 3 minutes timeout for report generation and hard caps of no less than 1 minute and no more than 15 minutes no matter the setting people use
Let me know if 3 minutes is not a high enough default or 15 is not max enough as you test it out