Skip to main content
Klipy tries to draft a reply in the background right after a message arrives, but that attempt can fail silently on long threads, rate limits, or safety filters, with no error shown. Use “Quick draft with Klipy” in the reply composer instead: it runs the same request on demand and shows an error if it fails, so you can retry.

​
What you’ll see

  • When Klipy’s background drafting works as expected, a suggested reply appears in the message thread within moments of a new email landing in a connected inbox.
  • When it fails, none of that shows up: no draft, no suggested next step, no summary attached to the message — it looks exactly like Klipy never attempted anything.
  • Nothing on the message indicates a failure specifically: no error banner, no “retry” button, no notification. The absence looks identical whether Klipy decided a reply wasn’t warranted or the attempt genuinely failed partway through.
  • This is most noticeable on messages you’d normally expect Klipy to handle: a reply to a prospect, a follow-up on an open thread, or any email in a conversation Klipy has drafted for before.

​
Why it happens

Klipy generates draft replies in the background as soon as a new message arrives in a connected inbox, using the same underlying process as every other Klipy draft — but it runs unattended, so nothing surfaces if it hits a problem. Three things commonly cause the attempt to fail:
  • The request hits a rate limit.
  • The thread has grown too large for the model to process (context grows with every reply, so long back-and-forth threads are the most common trigger).
  • The message content trips a safety filter.
When any of these happen, the interaction is marked as failed internally, but Klipy never renders that failure anywhere in the interface — no partial draft, no error message, no flag on the message. This is a known gap in Klipy’s background drafting today, not a sign that something is wrong with your account, your inbox connection, or the specific email; it’s a property of the thread and content, not your setup.

​
What to do now

1

Open the message in Klipy

Go to the message in your inbox or interaction feed where you expected a draft reply and didn’t get one.
2

Open the reply composer

Click reply to open Klipy’s composer for that message.
3

Use Quick draft with Klipy

Click “Quick draft with Klipy” inside the composer. This sends the same kind of drafting request as the background attempt, but on demand.
4

Retry if it fails

Unlike the background attempt, “Quick draft with Klipy” shows an explicit error if the request fails, so you know it didn’t work and can click it again to retry immediately. There’s no way to make the original background attempt retry itself — “Quick draft with Klipy” is the only path to a draft for that message once the background attempt has already failed.

​
When to contact us

Contact us if “Quick draft with Klipy” also fails repeatedly on the same thread after retrying. That points to something beyond the usual rate-limit or thread-length causes, and Klipy support can look into what specifically is blocking that thread.
No. Any reply Klipy drafts, whether from the background attempt or “Quick draft with Klipy,” is a draft you review and send yourself. Klipy never sends a reply on your behalf, including in Auto mode.
No. Once a background draft attempt fails, it stays failed. Klipy doesn’t retry it on its own — using “Quick draft with Klipy” in the reply composer is the only way to get a draft for that message.
Klipy’s draft request carries the message thread’s context along with it, and that context grows with every reply. Longer threads are more likely to exceed what the underlying model can process in one request, which is why long back-and-forth conversations are the most common trigger for a failed background draft.
You can’t tell the difference from the message itself — both look identical, with no draft and no indicator either way. If you expected a draft and don’t see one, use “Quick draft with Klipy” to generate one on demand rather than trying to determine what happened in the background.
Last modified on July 30, 2026