Thank you for the nice reports.
I would like to know what customizations in jsreport.config.json have you done except the mongo store?
What version of jsreport do you use?
Is it xlsx recipe or html-to-xlsx recipe you use?
Do you run jsreport inside docker or it runs directly?
Do you persist outputs using reports extension?
Can't your code in script or templating engine memory leak? In case you use http-server strategy.

In case you use http-server strategy for templating engines/scripts. Could you try to switch it back to the default dedicated-process temporary? Just that we try to isolate the problem.
Thank you

I attempted to delete the template using the API (using postman) and got this error:

I apologize, I didn't verify my advice and I see it is crashing also on the server.

Ok, so I fixed it. This is what I had to do...

Wonderful Idea! Thank you for sharing it.

Hi, you are limited just to the studio? In case you have access to the underlying store, and in case you use the default file system store, you should be able manually to remove the folder data/Group Excel and restart jsreport.

In case you don't have access. Your data structure is now corrupted and studio has issues with it.
However, you should be able to delete the template through API call.

You can call url like this and get the template _id
http://localhost:5488/odata/templates?$select=_id&$filter=name eq Group Excel
and then call DELETE on this
http://localhost:5488/odata/templates(the id of your template)

I'm not sure how corruption, the parent folder removal, happened.
However, the future version computes the parents dynamically and don't persist the reference. In other words, this shouldn't happen again.
Sorry for your troubles.

Thank you for the details. Could you email me your jsreport online subdomain/tenant name?
I would search our logs and check it out.
jan.blaha@jsreport.net
Thank you

Ah ok. Yes, that is how it works.

This is one way to allow access to all modules and file system from within jsreport.

new LocalReporting()
.UseBinary(JsReportBinary.GetBinary())
.Configure(cfg => cfg.AllowedLocalFilesAccess())

This allows just assets access

.Configure(cfg => {
  cfg.AssetsConfiguration = new AssetsConfiguration() { AllowedFiles = "**/*.*" };
  return cfg;
})

I will try to follow your install steps when I find some free time.

In the meantime, you can disable the extension locations cache in locations.json

node server.js --useExtensionsLocationCache=false

One of my reports has a lot of data and it therefore may take 30 sec or more to process in jsreportonline. Because of that, I've moved the report rendering to a worker process in AWS Lambda that, when complete, saves the report into my S3 bucket.

I am not sure I get it right. You moved the rendering to the lambda, but the mentioned errors are from jsreportonline?
You want to solve the jsreportonline issue and don't use lambda? Or you still use lambda in a combination with jsreportonline?
Or you use just lambda and this error is from it? Please elaborate on the details.

Not sure what kind of cluster you use exactly.
However, I am afraid this will need two licenses because both servers are production and running (booted/initialized) at the same time. It doesn't matter if they don't render at the same time.

This looks like a problem with the installation?
What steps did you follow when installing?
Can you try to delete node_modules and package*.json and install again?