Skip to main content

MARL support codes — Marl chat, files and the upstream model

What each of the 20 MARL codes means, and what to do about it.

J
Written by Jean-Baptiste COULON--CHABAGNO

Conversations, attachments, the file types Marl reads, and the provider Marl calls to answer you.

Find your code below — there are 20 of them. The digit between the letters and the dash says who can act on it: 1 is something you can change, 2 and 9 are Quavern's to fix, 3, 4 and 5 are decisions about access, 6 and 7 mean the service is in maintenance or has moved, and 8 points at the device or the network. MARL uses 1, 7, 9. The shape of a code is explained in How to read a Quavern support code.

Class 1 — Your request or your action

Check what you sent and the state of the account: the request itself, a quota, or the object it names. Correcting that and trying again is normally the whole fix.

MARL1-1001 — file_required

What it means. The request cannot go ahead without the file.

MARL1-1002 — empty_file

What it means. The file arrived with nothing in it.

What to do. Send content, then try again.

MARL1-1003 — invalid_file

What it means. Quavern refused the file: what arrived is not in the form this route accepts.

MARL1-1004 — invalid_encoding

What it means. Quavern refused the character encoding of the file: what arrived is not in the form this route accepts.

MARL1-1005 — unsupported_file

What it means. Quavern has not published what this code means. Its name does not settle it, and this page will not guess — indistinguishable from unsupported_file_type (MARL1-1006) by its slug alone, and the policy requires two conditions to be tellable apart.

What to do. Quote the code to support at [email protected], with the time and what you were doing, and you will be told what it means.

MARL1-1006 — unsupported_file_type

What it means. Quavern has not published what this code means. Its name does not settle it, and this page will not guess — indistinguishable from unsupported_file (MARL1-1005) by its slug alone, and the policy requires two conditions to be tellable apart.

What to do. Quote the code to support at [email protected], with the time and what you were doing, and you will be told what it means.

MARL1-1007 — pdf_too_long

What it means. The PDF is larger than this route accepts.

What to do. Send something smaller, or split it into several requests.

MARL1-1402 — plan_required

What it means. The plan this account is on does not include what was asked for. A paid plan does.

What to do. Change plan from the billing page, or ask the owner of the organisation to.

MARL1-1404 — conversation_not_found

What it means. The request named the conversation, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

MARL1-1409 — attachment_in_use

What it means. The attachment is still referenced somewhere else, so Quavern did not delete it: nothing that points at it should break.

What to do. Remove what still points at it first.

MARL1-1413 — attachment_too_large

What it means. The attachment is larger than this route accepts.

What to do. Send something smaller, or split it into several requests.

MARL1-2402 — team_plan_required

What it means. The plan this account is on does not include what was asked for. A Team plan does.

What to do. Change plan from the billing page, or ask the owner of the organisation to.

MARL1-2404 — attachment_not_found

What it means. The request named the attachment, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

MARL1-2409 — idempotency_conflict

What it means. The idempotency key sent with this request has already been used for a different request body. Quavern refuses to let one key stand for two different requests.

What to do. Use a new key for a new request, or resend the identical body under the same key.

MARL1-2413 — storage_quota_exhausted

What it means. The storage quota is used up — for the period in progress, or for what this plan allows.

What to do. Wait for the period to roll over, or move to a plan that allows more.

MARL1-3409 — request_in_progress

What it means. A request like this one is already running, and Quavern will not run two at once.

What to do. Wait for the first one to finish rather than sending it again.

MARL1-4409 — conversation_busy

What it means. The conversation is busy with something started earlier, and Quavern will not run two at once.

What to do. Wait for the first one to finish, then try again.

Class 7 — Stopped, moved, or an update is required

What you called has stopped, moved, or needs a newer version. Follow the migration or update notice rather than retrying.

MARL7-1503 — service_stopped

What it means. The service named has been stopped. This is not a moment of downtime; it is not served any more.

Class 9 — An indeterminate incident inside a known service

A service Quavern knows about failed in a way it could not classify. Keep the code and the time and send them to support.

MARL9-1502 — upstream_error

What it means. The model provider Marl calls failed. The failure is on Quavern's side, not in what you sent.

MARL9-2499 — stream_cancelled

What it means. The streamed answer stopped before it finished. Part of the work may already have been done.

What to do. Read the current state before starting again.

Still stuck

Write to [email protected] with the code, the reason, the time with its time zone, and the route you called. Never send a password, a token, an API key or full card details — support will never ask for any of them.

Quavern help reference: support-codes-marl/en

Did this answer your question?