Affected components
Update timeline
- investigating Mar 12, 2026, 12:16 AM UTC
We are currently investigating an issue that began at approximately 4:30 PM, where some claim runs are failing and returning the error message: “Error #0: Claims were found, but no transformation was found to generate the result.” Our technical teams are actively engaged and working to resolve the issue. Incident Managers will continue to provide updates here as additional information becomes available.
- investigating Mar 12, 2026, 02:14 AM UTC
We are continuing to investigate this issue.
- resolved Mar 12, 2026, 03:22 AM UTC
A fix has been implemented, and claim processing has been restored. Any claim runs that encountered the “Error #0: Claims were found, but no transformation was found to generate the result…” during this incident were not billed and will be automatically included in the next subsequent claim run. No additional action is required. We apologize for the disruption and appreciate your patience.
Looking to track AdvancedMD downtime and outages?
Pingoru polls AdvancedMD's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when AdvancedMD reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track AdvancedMD alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required