Hey Frank. Sorry for the slow reply here. We did some more investigation on our end and discovered we were mistaken that this error was caused by Autoptimize.
It’s actually being caused by Asset Cleanup. Our apologies. Initially when we deactivated AO it seemed to solve the issue. It must’ve been cached. Cheers!
