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

# Issue lifecycle

> What issue statuses mean and how issues move from open to resolved.

Issue status tells you where an issue is in the review and resolution process.

## Statuses

<AccordionGroup>
  <Accordion title="Open">
    Atlios is seeing the issue and it still needs review or action. This is the
    starting state for any issue a scan or Google Merchant Center surfaces.
  </Accordion>

  <Accordion title="Verifying">
    A fix, image workflow, or manual action has started, and Atlios is waiting
    for confirmation. Product and variant issues usually resolve after the
    Shopify update succeeds. Cross-catalog issues, and issues that Google needs
    to re-review, stay verifying until the next scan or sync confirms the
    condition is gone.
  </Accordion>

  <Accordion title="Resolved">
    Atlios no longer sees the issue, or an approved fix landed successfully.
  </Accordion>

  <Accordion title="Suppressed">
    Your team marked the issue as an intentional exception. Suppressed issues
    are kept for history, but they are not treated as active work.
  </Accordion>
</AccordionGroup>

## How issues move

Most issues follow this path:

<Steps>
  <Step title="Open">Atlios finds the issue during a scan or sync.</Step>

  <Step title="Action starts">
    You apply a supported fix, start a workflow, edit the product, or suppress
    the issue.
  </Step>

  <Step title="Verifying">
    Atlios waits for the fix, workflow, or next scan to confirm the issue is
    gone.
  </Step>

  <Step title="Resolved">
    A scan or action confirms the issue no longer needs active attention.
  </Step>
</Steps>

## One issue, one or more sources

The same problem can be flagged by more than one source. If your Shopify scan
and Google Merchant Center both flag the same field on the same product, Atlios
treats it as **one** issue with both source badges, not two separate rows. It
counts once everywhere, and resolving it clears both signals.

## Reopened issues

An issue can reappear if a later scan finds the same problem again. This can
happen when catalog data changes, a product is edited, or a previous fix no
longer applies.

<Tip>
  Use the issue activity section to understand when an issue was first seen,
  fixed, suppressed, reopened, or moved into verifying.
</Tip>