diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 256624cf..5fb01934 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -157,6 +157,7 @@ Coded by importance
 	or, is it possible to write out the config.json from the installer and not include it as a physical file??
 		This way it can properly write out whatever paths necessary in single installer at least
 
+- 1 todo: ideally installer should have a commented out jwt secret that wont' take effect but has text like "EDITME AND UNCOMMENT" or whatever
 
 
 
@@ -248,6 +249,44 @@ TODO: 1 BETA DOCS:
 ██   ██ ███████ ██       ██████  ██   ██    ██    ██ ██   ████  ██████  
 
 
+---
+- 1 issue: New reporting process is causing linux server to reboot with large reports and not much info as to why 
+theory: I'm running out of memory, however the do log doesn't show that so maybe need to do free mem check while running
+	potential fix: 
+		need to limit chromium ram usage somehow or check the size of the data and if it's anywhere near the server ram then bump it up or...?
+		If it has to use disk memory, even if it could, that would be painfully slow so...hmmm.
+		really low timeout on low ram server to avoid this whole thing??
+		ram check constantly throughout render process and bail if gets within 80% of max maybe??
+
+
+OPEN QUESTIONS:
+Can I get the size of the data being sent to the report somehow and at least log it?
+Why is chromium process triggering all of AyaNova to restart hard??
+	some kind of linux thing??
+
+
+TRY: try temporarily bumping the ram if can in d.o. and see if it goes through
+- try old server code from prior release and see if it crashes when doing that many wo??
+	maybe try in vm first can play with all manner of shit there and starve or add ram to figure out
+
+
+TESTING INFO:
+	if select 500 wo it *will* try to complete but timeout so no crash there
+		memory definitelhy hits 99% on this one but doesn't crash just times out
+
+	bumped linux server to 2gb ram and was easily able to run 500 pages but it took 78% of ram to do it (I think)
+	
+
+
+	if select 1000 wo it will crash 
+		mayb
+
+
+-----
+
+
+
+
 - 1 todo: add the caching technique to *all* the other getreportdata methods as was done with workorder 
 
 
@@ -266,6 +305,13 @@ TODO: 1 BETA DOCS:
                                            
 
 
+- 1 todo: figure out why a wait display in clien tpage (printing for eg) causes the browser to go wild using up cpu cycles, like WTF is that about
+	animation, graphics, ???
+	Maybe I need to forego that for something more efficient to show waiting like a non animated or simpler thing
+
+- 1 todo: server logs display needs a download option to just download the log file rather than copy it as a trace can be enormous and copy is pushing the limit
+	also it would be cool to be able to search it right on the page I guess browser search can do that... hmmm..
+
 - 1 todo: Unlicensed doesn't allow any troubleshooting info, make sure that the user can still get to ops when unlicensed and view server configuration or whatever 
 	is required to troubleshoot failed install
 - 1 bugbug?:open vendor, print report, go back it shows as savable all of a sudden despite no changes made in UI, also does not give dirty save prompt when leave it even though save icon is showing enabled bold
@@ -446,9 +492,14 @@ todo: 1 When there is a rendering issue with chromium browser startup the server
 	this is because it was written expecting any error was a template error not a starting chromium error so need to look there in the exception handler 
 	would rather not log report template issues to the server log but anything else structural should be
 
-todo: 2 Log levels are all over the place at the server, follow proper guideance and adjust them as per:
-	https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.loglevel?view=dotnet-plat-ext-6.0
-	specifically there are a lot of log debugs that should be traces and maybe missing log criticals level for server stopping shit
+todo: 2 Log levels are all over the place at the server
+	After attempting to diagnose an issue I'm leaning towards save trace for when need to see sql and put all other shit above trace completely
+	the sql kind of eats up all the space, however I guess that's useful, but it's so huge it's concerning and hard to deal with
+	needs a ponder and decide what is best for tech support purposes
+
+
+todo: 2 add an ops notification on server boot
+	this way can catch if the server is rebooting regularly in linux or iis when the processmanager restarts it
 
 todo: 2 wrap this error in a debug build block before release:
 	2021-12-22 16:19:07.0290|ERROR|AyaNova.Biz.TranslationBiz|********* GetSubsetAsync problem: Duplicate keys: WorkOrderItemPartQuantity)