SendGrid troubleshooting

Each table lists the message Maiilo shows and what to do about it.

When connecting fails

In every case below, your key was not stored.

What you see	What to do
That does not look like a SendGrid API key. They start with “SG.” and are shown only once when created.	You probably pasted the wrong value, such as a key ID or a truncated copy. A SendGrid key starts with SG.. Maiilo catches this without contacting SendGrid.
The API key has leading or trailing whitespace — re-copy it.	A space or line break came along with the paste. Copy the key again without the surrounding whitespace.
SendGrid rejected this API key. Check that it is correct and still active.	The key looks right but SendGrid does not accept it. Usually it was deleted, or it belongs to a different account than you think. Create a new key and try again.
This key authenticated but lacks Template permissions. Create a key with Full Access, or with read/write access to Template Engine.	The key is real but too narrow. Add Template Engine read and write in SendGrid, or create a Full Access key. See the permissions reference.
Could not reach SendGrid. Check your connection and try again — your key was not stored.	A network problem between Maiilo and SendGrid, not a problem with your key. Try again in a moment.
SendGrid is rate limiting requests. Try again in a moment.	Too many requests reached SendGrid at once. Wait a minute and retry.
SendGrid is having trouble right now. Try again shortly.	SendGrid returned a server error. Check status.sendgrid.com and retry once it is clear.
ESP integration is a Pro feature.	Connecting needs Pro. Start a Pro trial or upgrade, then connect.
Credential encryption is not configured on this server. Your key was not stored.	A problem on Maiilo’s side. Maiilo refuses to store a key it cannot encrypt. Contact support.

When a push fails

What you see	What to do
SendGrid rejected this template. This usually means an unclosed {{ in the HTML — SendGrid reads {{ }} as Handlebars and cannot parse a template with a stray one.	Look for a lone {{: a variable you started typing and did not finish, or a brace in body copy. Fix it, publish, and push again. See Your variables in SendGrid.
SendGrid rejected your API key. Reconnect SendGrid with a current key.	The key worked when you connected it and does not now, usually because it was deleted in SendGrid. Replace the key.
Your SendGrid key lacks Template permissions.	The key’s permissions were narrowed after you connected. Add Template Engine read and write again, then reconnect.
SendGrid is rate limiting requests. Try again in a moment.	Maiilo already retried a few times. Wait a minute and push again.
This template is too large for SendGrid.	SendGrid limits a template to about 1 MB of HTML. Reduce the size, publish, and push again.
Publish this template before pushing it. SendGrid receives the published version, not the draft.	Publish first. Maiilo only pushes published versions.
Add a subject before pushing to SendGrid. SendGrid requires a subject on every template version.	Add a subject with Edit details, publish, then push. Nothing was sent to SendGrid.
Publish again to include your subject. SendGrid receives the published version, and it was published without one.	You added a subject after publishing. Publish, then push. Nothing was sent to SendGrid.
Pushing to SendGrid is a Pro feature.	Your plan does not include pushing, or your trial ended. Templates already in SendGrid are not affected. Upgrade to push new versions.

Every attempt, including failed ones, is recorded in the template’s push history. A template whose latest push in the last 7 days failed is listed on Needs Attention until a later push succeeds.

The SendGrid card says “Needs attention”

The key worked when you connected it, but SendGrid has since rejected it, usually because it was deleted or its permissions were narrowed. Create a new key and replace the stored one.

Need a hand?

Email [email protected].