What triage routes are #
After a diagnosis identifies what broke, the triage step tells you what to do about it. Loupely doesn’t offer a single generic “contact your developer” response. The triage route is specific to what the diagnosis found, and it routes you to the right action for that specific failure type. For Loupely Lens, the triage includes a ready-to-paste CSS override when one is safe to provide, or a developer handoff package when the fix requires code changes.
The 5 Loupely triage routes #
Rollback. The diagnosis identified a specific plugin update as the likely cause. The triage step provides the plugin name, suggests deactivating it, and links to the article on rolling back plugin updates. This route is offered when a recent update correlates directly with the failure pattern in the capture.
Plugin conflict. Two or more plugins are producing conflicting signals. The triage step names the plugins involved and suggests isolating the conflict using the Health Check troubleshooting mode. This route is offered when the correlation rules identify a known conflict pattern between specific plugin types.
Hosting. The failure is in server configuration: PHP Memory Limit, PHP version incompatibility, a blocked loopback request, or a REST API block at the server level. The triage step provides specific language to use with your hosting provider’s support team, based on what the capture identified.
Cache clear. The failure pattern matches a stale cache state: an expired nonce being served from cache, a checkout page with cached cart state, or a static resource that isn’t updating. The triage step tells you which cache layer to clear and how.
Developer handoff. The failure requires code changes that aren’t safe to apply without development expertise. The triage step packages the capture data with a pre-written message explaining the failure to a developer. The developer receives the specific error, file path, and context without needing back-and-forth to reproduce the problem.
Loupely Lens triage routes #
Lens triage routes are specific to CSS failures. When Lens identifies a conflict between two stylesheet origins, the triage may provide a ready-to-paste CSS override scoped tightly to the specific element. When the fix requires changing a setting in a page builder or theme options panel, the triage names the exact panel and field. When the fix requires a developer (because the winning rule is deeply nested in a framework’s CSS and safe overriding requires knowledge of that framework’s selector structure), the triage provides a developer handoff package with the full cascade context.