It looks like it might be a customization causing this.
Have you tried to debug the report while it is running?
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.