How to read your error log

Settings → Logs lists what failed in your workspace: a message that didn't send, a flow step that stopped, a webhook delivery or integration run that failed, an API request that was refused, and a channel that disconnected. Each kind of failure appears once with a count, so a problem that repeats a hundred times is one line, not a hundred. It's for owners and admins, and it appears only where the error log is turned on for your workspace — it isn't on for every workspace yet.

The log records what failed and where. It never keeps a message's text, a customer's name or a password.

Find what failed

1. Open Settings, then Logs. A red count on Logs in the menu (or a red dot on Settings while that section is closed, and on More on a phone) means new critical or error entries since you last looked.
2. Read the counts under the filters — Critical, Error, Warning and Info — to see how much of each there is in the time range you're viewing.
3. Narrow the list with Level, Source, Channel and Time range (Last 24 hours, Last 7 days or Last 30 days). Start with Level set to Critical: those are the ones that stop sending. Reset filters puts the list back.
4. Select an entry's title to open it.

Opening the log with no filters clears the red count. A filtered view doesn't, because it might be hiding a newer critical entry — and neither does a time range that hides one (an entry older than Last 24 hours shows, say).

Get an email when something fails

1. On Settings → Logs, click Email alerts at the top of the page. It opens Error log emails under Settings → Notifications.
2. Leave Critical — sending or a connection stopped on to be emailed straight away when sending stops. A problem that already has its own alert, like a disconnected channel, isn't emailed twice.
3. Turn on Errors and Warnings for one email an hour that lists what failed and how often, sent only when something new failed. Each switch saves as you flip it.

What each level means

• Critical — sending or a connection has stopped. Fix this first.
• Error — something didn't go through, and HyperDM won't try it again.
• Warning — something went wrong, but HyperDM is retrying or working around it.
• Info — something recovered, such as a restriction that was lifted. Nothing for you to do.

Open an entry and retry it

The panel that opens shows the same "what to do" line, how many times it happened, when it was first and last seen, and any numbers that help, such as the Response code or the Attempt.

1. Follow its links to where it happened: Open the automation, Open the contact, or the delivery log or Integrations page the failure came from.
2. For a failed webhook delivery or integration run, fix the cause first, then select Retry. The panel says whether the retry was accepted, or why it can't be yet (say, the integration needs reconnecting first); the result itself shows on the page the failure came from. Other entries have no Retry — fixing the cause is the retry.
3. Select Close, or press Escape.

The panel's address opens the same entry, so you can send it to another owner or admin of the workspace. If the panel says Couldn't open the entry, the log didn't load just then: try again in a moment. Entry not found means the entry is no longer in the log.

What to do about the common entries

Read a restriction in the platform's own words

The Restrictions tab is the history of Instagram, Facebook and WhatsApp warning, limiting or blocking one of your accounts, and of those restrictions being lifted.

1. Select the Restrictions tab.
2. Read each row's Status — Warning, Limited, Blocked or Lifted — and when it happened.
3. Where the platform gave a reason, it's under In the platform's own words, exactly as they wrote it. Appeal from the platform's own tools; HyperDM can't lift a restriction for you.

How long entries are kept

Entries are kept for 30 days, and restriction history for a year.