Skip to main content
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

Meta WhatsApp Business API

Most “messages not sending” or “delays” issues turn out to be Meta-side. Check this first.

HubSpot status

Failed workflow actions and disconnected-integration banners usually trace back to here.

Flowella incidents

Operational-category notifications broadcast incidents and maintenance windows for your org.

Contact support

Open a ticket if none of the above explains what you’re seeing.

Meta WhatsApp Business Platform

Check Meta WhatsApp Business API status 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.
Subscribe to operational events by email under Settings → Notification preferences so you hear about incidents without needing the app open.

HubSpot

A HubSpot incident will surface in Flowella as failed workflow actions or a disconnected integration banner on Settings → HubSpot. Check HubSpot status 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.
  • For outbound webhooks that aren’t firing, check the delivery log under Settings → Webhooks. See Webhooks.
  • For HubSpot workflow failures, check the workflow’s action history in HubSpot. See HubSpot sync failures.

Reporting an incident to Flowella

If you believe Flowella is having an incident that isn’t reflected in your notifications, contact 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.