I believe there’s an underlying issue that first showed up around 2024.x and has become much more common in 2025.2, where custom reports fail with a “/SaaS####PilotSSRS_######/reports/customreports/Tenants/######/… cannot be found” error. From what I can tell, it’s related to how the SystemFlag is set in the Ice.ReportStore view. The function that drives this flag passes the print program path as a 100-character parameter and checks for an exact match in Ice.CustomReportStore. If it doesn’t find one, it marks the report as a system report (SystemFlag = 1), which seems to prevent the report from running, even when the RDLs exist on the server.
A good sign that you’re hitting this problem is if the error message includes a very long full path that starts with something like /SaaS####PilotSSRS_######/reports/customreports/Tenants/######/… the bolded portion adds about 40–41 characters to the path for cloud customers, which pushes many print program values past the 100-character limit on that SystemFlag function. Earlier versions only recorded relative paths to the CustomReportStore table, so this wasn’t as noticeable, but now that it records the full path, the function truncates it and can’t match correctly.
Based on testing, the only reliable fix I have found is to make sure your full print program path, including the tenant prefix, folders, and report name, stays under 101 characters. The Copy function in Report Style Maintenance can still work as a temporary workaround (since it skips the upload process that writes a record to the CustomReportStore table), but once you re-upload, the issue returns if the path is too long. Since the full path adds about 40 characters, keeping your report style name around 50-55 characters or less seems to prevent the problem. I’ve shared these findings with Epicor Support, and it’s currently under review.