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

# Status and incidents

> Where to check whether a WhatsApp problem is on Flowella's side, on Meta's side, or in your own integration — status pages, dashboards, and known incidents.

When something doesn't look right, the first question is usually: **is this me, Flowella, or Meta?** Use the status pages below to triage.

## Status pages at a glance

<CardGroup cols={2}>
  <Card title="Meta WhatsApp Business API" icon="message-circle" href="https://metastatus.com/whatsapp-business-api">
    Most "messages not sending" or "delays" issues turn out to be Meta-side. Check this first.
  </Card>

  <Card title="HubSpot status" icon="plug" href="https://status.hubspot.com">
    Failed workflow actions and disconnected-integration banners usually trace back to here.
  </Card>

  <Card title="Flowella incidents" icon="bell" href="/app/notifications">
    Operational-category notifications broadcast incidents and maintenance windows for your org.
  </Card>

  <Card title="Contact support" icon="life-buoy" href="https://flowella.io/support">
    Open a ticket if none of the above explains what you're seeing.
  </Card>
</CardGroup>

## Meta WhatsApp Business Platform

Check [Meta WhatsApp Business API status](https://metastatus.com/whatsapp-business-api) first. If Meta is reporting an active incident, sends will retry once the platform recovers — there is nothing to fix on the Flowella side.

## Flowella

If Meta looks healthy and Flowella itself appears down or sluggish, in-app notifications are our primary signal. Open **Notifications** (or the bell icon) and look for **Operational** category notifications — we use these to broadcast incidents and maintenance windows that affect your org. See [Notifications](/app/notifications).

<Tip>
  Subscribe to operational events by email under [Settings → Notification preferences](/settings/notification-preferences) so you hear about incidents without needing the app open.
</Tip>

## HubSpot

A HubSpot incident will surface in Flowella as failed workflow actions or a disconnected integration banner on **Settings → HubSpot**. Check [HubSpot status](https://status.hubspot.com) before raising a ticket with us.

## Your integration

If neither platform is reporting an incident:

* For **API issues**, check the response body — Flowella returns a structured error envelope. See [API introduction](/api-reference/introduction).
* For **outbound webhooks** that aren't firing, check the delivery log under **Settings → Webhooks**. See [Webhooks](/settings/webhooks).
* For **HubSpot workflow** failures, check the workflow's action history in HubSpot. See [HubSpot sync failures](/troubleshooting/hubspot-sync-failures).

## Reporting an incident to Flowella

<Note>
  If you believe Flowella is having an incident that isn't reflected in your notifications, contact [support](https://flowella.io/support) with:

  * Your organisation name
  * A timestamp range (UTC) when you first noticed the issue
  * A description of what's broken (with a screenshot if possible)

  We'll respond on the channel you contacted us on and update affected orgs via in-app notifications and email.
</Note>