Connect what you
already use.

Every reason an event can show

The Flows page prints one short reason per event or delivery. This is the whole vocabulary — there is no other error text.

• fetch failed — We could not download the recording from the link the provider sent — the link had expired, it needed a login we do not hold, the file was over 300 MB, it pointed at a private address, or the server did not answer. We retry a few times before giving up. If your recordings need a login, set "If the recording needs a login" on the source.
• audio files only — The file was not audio — a picture, a document, or (except from a Drive folder) a video. Only a Drive folder source accepts video; every other door wants an audio file.
• audio unreadable — The file was named like audio but could not be decoded: empty, cut short, or not the format its name claims. Not retried. Send the recording again from the provider.
• no minutes — Your workspace had no pooled minutes left, so we did not download the recording. Skipped, not retried. Top up the pool and have the provider send the recording again.
• processing failed — The recording came in but something on our side failed after that. We are alerted automatically; if it keeps happening, write to support@getmeetnotes.com with the reference shown on the Flows page.
• sender not allowed — An email arrived from an address that is neither a member of your workspace nor on the source's allowed-domain list. Add the domain under "Save senders" on the card, or send from a workspace address.
• sender not verified — An email came from an allowed address, but the mail itself did not prove it: it failed SPF for the sender's domain and carried no DKIM signature from that domain. A From: line can be typed by anyone, so we only trust the one the mail system vouched for. Send from the domain's own mail server (Google Workspace, Microsoft 365 and the like pass this by default), not a forwarder that rewrites the message.
• unsigned request — The post carried no valid signature. Either the signing secret pasted on the source does not match the one in the provider's console, or the provider is posting from a place that does not sign. Paste the current secret again; nothing unsigned is ever accepted.
• file too large — A file in the Drive folder is over 2 GB — almost always a video nobody meant to transcribe. Skipped. Export the audio track, or trim the video, and drop the smaller file in.
• delivery failed — Your endpoint, channel or CRM did not accept the post — it was unreachable, answered with an error, or timed out. We retry, then mark the delivery failed. Use "Send test" on the destination after you have checked the URL or token.
• no matching contact — No contact in your CRM matched the email or phone number we had for the customer on that call. Skipped, not retried, no contact is created. Check the number format on the contact, or that the provider sends the caller's number at all.
• recording not ready — The provider told us about the call before its recording was finished. Skipped for now; when the completed recording is posted the same reference is revived and processed once.
• workspace suspended — The workspace has been paused, so its sources accept nothing until it is restored. Write to support@getmeetnotes.com.