Email queue

Answer the question "did the client receive it?" with fact. Instead of guessing, you see the attempt, the time and the server error when there was one.

Each company sees the emails sent on its behalf — user invitation, daily briefing, collection, notification. The platform (BMCode) sees the whole set, because it operates the sending service.

The envelope on the row opens the e-mail with the sending data, the body and the error, if any. To find a failed e-mail, filter the status by ERRO and search by recipient.

The e-mail enters a queue and goes out through its own process, with a retry in case of temporary failure. This keeps the user's screen from getting stuck waiting for the e-mail server to respond.

Authentication error, unverified sender and domain without sending authorization are the most common causes — and all of them are resolved in the e-mail configuration, not in the queue.

An email that fails is recorded with the error. If the same recipient fails repeatedly, the problem is almost always the registered address — and each repeated attempt worsens the platform's sending reputation. Correcting the record solves both.

Sent means the server accepted it. If the client didn't receive it, the message may be in spam or blocked due to domain reputation — it's worth checking your domain's authentication configuration.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

A message gets this error when the transmission started and the system did not know how it ended — because the server went down midway, or because the connection was lost after the provider had already accepted the message. There is no way to ask the provider whether it delivered. That is why the platform does NOT resend on its own: resending by reflex is what makes the same email reach the customer twice. What to do: confirm with the recipient or through their history whether the message arrived; if it did not, resend it manually from this screen. If this error appears frequently, let support know — it usually indicates the server is being restarted while the system is in use.

This list is read-only: records cannot be edited or deleted here, because they are evidence of what happened. The top search looks in the text fields; the Filters button opens the side panel with the cuts (status, type, company…); the combination can be saved as a view and reopened with one click. In the ⋮ menu, Excel and PDF take the whole filtered set — not just the page on screen — and "export everything" asks for your password. The eye on each row opens the detail on the side.

Search by the recipient's email. Status "sent": it left here — ask them to check spam and confirm the address. "Waiting": it is in the queue and goes out in the next cycle. "Failed": the reason appears on the row (nonexistent address, mailbox full) — correct the record and resend.

There's no resend button on this screen — it's the window into the queue, not the trigger. Reprocessing of failures is automatic: the Attempts column and the date of the last attempt show the system insisting. If the recipient was wrong, fix the record and repeat the action that generated the e-mail (resending the invitation, for instance) — this creates a new entry in the queue. The exact failure error is in the e-mail detail, Error tab.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".