What creates a notice
A notice is created when a storefront request degrades because of an integration problem, not a Layers outage. The four notice types are:
Repeated occurrences of the same problem roll up into a single notice. Each row shows the offending subject (the facet code, selector, or context key), the request that triggered it, an occurrence count, and when it was first and last seen.
Notifications
When a notice opens for the first time, Layers sends one notification to the inbox in the dashboard header. Notifications go to every team member whose role includes the Stream live search logs permission. Occurrences are aggregated per problem type, so a theme deploy that trips several bad facet codes produces a single notification such as “6 facet codes requested but not enabled”. A notice that keeps recurring does not notify again — you are only notified when a notice opens or reopens.Review and manage notices
- Go to Settings > Developer Notices, under Developer.
- Use the search box to filter by subject or problem code, or filter by status.
- Read the How To Fix column for the remediation, and the Request column to see which storefront call triggered the notice.
- Resolve — mark the notice as fixed. If the storefront asks for the same thing again, the notice reopens automatically and you are notified again.
- Dismiss — silence the notice permanently. It will not reopen or notify again, even if the problem keeps happening.
Automatic resolution
Layers resolves open notices automatically once they have not occurred for 7 days and clears their inbox notifications. Dismissed notices are never changed.Next steps
- Manage roles and permissions to control who sees developer notices.
- Manage API access to review the tokens your storefront uses.
- Contextual information to learn what the
contextpayload accepts.