avg response time is back >200ms ... ugh. Performance is probably going to have to be routinely revisited.
Just pushed a fix. Turned out to be an issue where jobs sat payment records are numerous and my query wasn't specific enough to filter them out ... so lots of records were getting scanned that didn't need to be = lots of time.
reply