> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uselayers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review developer notices

> Find and fix storefront requests that ask Layers for facets, attributes, or context your store cannot answer, using the Developer Notices page.

The **Developer Notices** page records storefront API requests that asked for something your store cannot answer. Examples include a facet code that isn't enabled, an attributes selector that couldn't be parsed, or a context field that failed validation. Layers still serves these requests, but without the part it couldn't honor. Each notice tells you exactly what was dropped and how to fix it.

Viewing and managing developer notices requires the **Stream live search logs** permission, which is available to the Owner, Admin, and Developer roles.

## 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:

| Problem                  | What happened                                                                                                                                                      | How to fix it                                                                                                 |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Facet not enabled**    | A requested facet code exists for your store but is not enabled as a storefront facet.                                                                             | Enable the attribute as a filterable facet, or stop requesting it from the storefront.                        |
| **Facet not recognised** | A requested facet code matched no known attribute. If the code only differs from a real facet by letter case, the notice says so — facet codes are case sensitive. | Check the code against your store's configured facets and match it exactly.                                   |
| **Attributes selector**  | An `attributes` selector in the request could not be parsed, so field projection was skipped.                                                                      | Fix the selector syntax in the storefront request.                                                            |
| **Context field**        | Part of the request's `context` payload failed validation and was dropped, so personalization ignored it.                                                          | Send a value matching the documented [context data structure](/engine/contextual-information/data-structure). |

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

1. Go to **Settings > Developer Notices**, under **Developer**.
2. Use the search box to filter by subject or problem code, or filter by status.
3. Read the **How To Fix** column for the remediation, and the **Request** column to see which storefront call triggered the notice.

Each open notice offers two actions:

* **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.

Select multiple rows to resolve or dismiss notices in bulk.

## 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](/help/configuration/manage-roles-and-permissions) to control who sees developer notices.
* [Manage API access](/help/configuration/manage-api-access) to review the tokens your storefront uses.
* [Contextual information](/engine/contextual-information) to learn what the `context` payload accepts.