Your software
My Mautic version is: 7.1.0
My PHP version is: 8.3.21
My Database type and version is: 10.11.11-MariaDB with mysql 15.1
Your problem
I wanted to use the new draft Feature of Mautic and from user perspective I am very confused.
As an Integrator I found the following: I Saved an email as a draft und made change to the email content. Now there are to scenarios, either I save via the tick in the Builder or click on the cross and save via “Save & Quit”. In the first case the email got saved in the email entry in the table “emails” of the database so the next email sent is edited, but in the second case the email got saved in the table “email_draft” so the next email sent is not edited. As a User I would expect that both ways act the same.
Agreed, that’s confusing, and it reads like a bug, not intended behaviour. With a draft active, every save path should write to `email_draft` until you explicitly **Apply/Publish draft**. The builder’s tick (“apply”) writing straight to `emails` means a half-finished change can go live in the next send.
Until it’s fixed, to be safe:
- With an active draft, only use the builder’s close (X) → **Save & Quit**, and use the draft’s *Apply draft* action when you’re ready, or
- Don’t keep a draft open on emails that are actively sending (campaign or continuous segment emails). Clone the email instead and swap it in.
Since you already traced exactly which table each path writes to, it would be great to open a GitHub issue with these steps (Issues · mautic/mautic · GitHub) and link it here. That’s precisely the reproduction the devs need.