That makes sense. There is a timeout to prevent bad user scripts from hogging processing power, but the initial indexing of large datasets for lookup might exceed that under heavy load. I'm going to try exempting that work from the timeout and see if it cures the issue. I'll pos here once that's available. Thanks for reporting!
↧