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

# Troubleshooting

> Common issues and what to check first.

<AccordionGroup>
  <Accordion title="My Daily Brief shows a holding banner instead of a real read" icon="ban">
    Your workspace is below the data-completeness threshold. Forepost won't fabricate a brief from missing numbers — see [Honest "I don't know"](/reference/honest-no-data).

    **Fix:** open Settings and fill in the metrics named in the banner. The threshold is 4 of 5 core metrics plus at least 1 named agent.
  </Accordion>

  <Accordion title="I imported a CSV but no metrics populated" icon="file-csv">
    Forepost couldn't find a usable `created_at` column. Open **▸ Adjust column mapping** below the upload area and pick the right column manually.

    If you've already mapped `created_at` and the preview is still blank, the column values aren't parsing as dates. Check that the CSV uses ISO timestamps or a common locale format (e.g. `2026-05-09T12:00:00Z` or `09/05/2026 12:00`).
  </Accordion>

  <Accordion title="My Daily Brief email landed in spam" icon="envelope">
    This is almost always a *first-time-sender* learning phase issue. Once:

    1. Mark the message as **not spam** in Gmail/Outlook.
    2. Add `noreply@forepost.ai` to your contacts.

    Future briefs will deliver to inbox.

    If it happens consistently after a week, it's a DNS misconfiguration on the receiving end. Forepost shows `dkim=pass`, `spf=pass`, `dmarc=pass` in the email's authentication headers. If `dmarc=fail` appears, contact [kian@forepost.ai](mailto:kian@forepost.ai).
  </Accordion>

  <Accordion title="&#x22;Send brief now&#x22; returns an error" icon="triangle-exclamation">
    | Status                                   | Meaning                                                 | Fix                                            |
    | ---------------------------------------- | ------------------------------------------------------- | ---------------------------------------------- |
    | 400 with a `missing` field               | Workspace below the completeness threshold              | Fill in the named fields in Settings           |
    | 403 "Email not verified on this account" | Subscription email isn't verified on your Clerk account | Verify it in your account settings, then save  |
    | 429 "Too many sends"                     | You've hit the rate limit (5/hour for manual sends)     | Wait an hour. Scheduled sends aren't affected. |
  </Accordion>

  <Accordion title="I'm not receiving Weekly Watch even though it's enabled" icon="calendar-week">
    Three checks:

    1. The digest only sends on Mondays in your local timezone. Today might just not be Monday.
    2. It only sends if your workspace is data-complete that morning. See above.
    3. It only sends once a week — if the previous one was sent within the last 6 days, the next won't send yet.

    Use **Settings → Delivery → Send digest now** to confirm the path works end-to-end.
  </Accordion>

  <Accordion title="Triage isn't drafting replies for new conversations" icon="inbox">
    Three checks:

    1. **Intercom must be connected.** Settings → Integrations → Helpdesk integrations. The OAuth token is required for both polling and sending.
    2. **Triage must be enabled.** Settings → Integrations → Triage. The toggle gates the cron poll and the nav item.
    3. **The poll cadence is every \~10 minutes.** Click **Poll Intercom** on the Triage page to force one immediately.

    If you see polls landing but no drafts, the Anthropic API may be rate-limited or down. The poll's response body shows `drafted: 0` in that case.
  </Accordion>

  <Accordion title="A Triage draft failed to Send to Intercom" icon="paper-plane">
    Two common causes:

    1. **The conversation closed in Intercom** since the draft was generated. Triage will mark it `resolved` on the next poll. Discard the draft.
    2. **Your Intercom token expired or was revoked.** Reconnect via Settings → Integrations → Helpdesk integrations.

    The error message bubbled up from Intercom's API appears in the page.
  </Accordion>

  <Accordion title="Accounts → Sync from Intercom returned 0 accounts" icon="users">
    Intercom returned no companies for your workspace. Two checks:

    1. Your Intercom workspace actually has companies attached (some teams skip the company model). Forepost's sync uses the Companies API; if you only use individual contacts, this won't populate.
    2. The OAuth scope you authorised includes company read. Reconnect Intercom to re-grant scopes if needed.
  </Accordion>

  <Accordion title="The forwarded email opens with no recipient" icon="user-slash">
    That's expected. Forepost composes the subject and body but doesn't fill in the To: line — you choose the recipient in your mail client. Intentional: the email goes from your account, with your signature.
  </Accordion>
</AccordionGroup>

## Still stuck?

Email [kian@forepost.ai](mailto:kian@forepost.ai) with:

* The page or action that broke
* A screenshot of the error if there is one
* Your account email address

Beta-period response is fast.