How to Fix Common Creaiter Problems

A publish failed

Publishing involves your site, your credentials, and the post itself. Work from the outside in.

1. 01Confirm your website connection is still active in Settings, and reconnect if it is not.
2. 02Open your site in a browser and confirm it loads normally and is not in maintenance mode.
3. 03Confirm the connected account still has permission to publish. Role changes and password resets break this quietly.
4. 04Confirm you are publishing to the site you meant, if more than one is connected.
5. 05Check whether the post partly made it. A publish can fail after the post was created, leaving a draft sitting on your site.
6. 06Fix the connection, then retry the publish rather than regenerating the post. The draft is still in your repository with its status intact.
7. 07If it fails twice in a row with a working connection, stop retrying and contact support. Repeated attempts can leave duplicate drafts on your site.

A connection shows disconnected

Connections expire. Tokens have lifetimes, passwords change, and permissions get revoked by someone else on the team. Disconnected is usually accurate, and usually easy to fix.

Check which word the badge uses before you change anything. Connected means a real check passed. Last check failed means one ran and did not. Configured means a key is saved and nothing has tested it yet — that is not a fault, and re-entering a key on the strength of it is how a working connection gets broken.

1. 01Press Test all under Connection Health first. It is free, and it turns a Configured into a real answer for your API keys, your Google connections and your website.
2. 02For SMS, use Verify now on the Twilio card instead. Test all does not check it.
3. 03Reconnect from Settings, if a check actually failed. That is the fix in most cases.
4. 04If reconnecting fails, sign in to the service directly and confirm the account still works and still has access.
5. 05For Google, confirm you are signing in with the account that has access to the property, not a personal account that looks similar.
6. 06For your site, confirm the address has not changed, including a move to https or a new domain.
7. 07If it reconnects and drops again within a day, report it. Contact support with the service name and when it started.
8. 08Do not keep working against a disconnected integration. Scheduled work that depends on it fails at the scheduled time, which is much harder to notice.

Analytics data is missing

Analytics is late by design, so check the calendar before you check the connection.

1. 01Search Console runs a few days behind. Recent days being empty is normal, not broken.
2. 02GA4 needs time to process, so today is always incomplete.
3. 03Confirm the connected property is the right one. Accounts often hold several with similar names.
4. 04Confirm the property was collecting data during the range you are asking about. A new property has no history and no tool can create one.
5. 05Confirm your site is actually sending data to GA4, by checking in Google directly.
6. 06If the dates are old enough, the property is right, and Google shows data that Creaiter does not, contact support with the property name and the date range.

A generation seems stuck

Generation runs on your AI provider key, so a stall is usually the provider rather than the chat.

1. 01Give it a moment. Long content on a large model genuinely takes time.
2. 02Check your provider dashboard for credit, a spending cap you hit, or a rate limit.
3. 03Check the provider's status page for an outage.
4. 04Try a short request. If a one-line question answers instantly, the key is fine and the long job was the problem.
5. 05Try a different model or provider if you have more than one key added.
6. 06If the operation offers a way to cancel, use that rather than reloading the page, so the work stops cleanly.
7. 07If the same request stalls twice, contact support and tell us exactly what you asked for.

An email did not arrive

Almost always Resend, and almost always the sending domain.

1. 01Confirm your sending domain is verified in Resend. An unverified domain is the number one cause of a first campaign that never lands.
2. 02Confirm the Resend API key in Settings is current and has not been rotated.
3. 03Check the spam folder, on the actual receiving address rather than a forwarded copy.
4. 04Check the segment you sent to actually contained people. An empty segment sends nothing and looks like a failure.
5. 05Check whether the recipient previously unsubscribed. Unsubscribed contacts are excluded, and that is correct behavior.
6. 06Check Resend's own logs, which show what was accepted and what bounced.
7. 07If Resend shows it as delivered and the recipient still does not have it, the problem is on the receiving side, usually a corporate spam filter. Sending from a verified domain with a real reply-to address is the fix that holds up over time.

When to contact support, and what to send

Contact support when you have worked the list for your symptom and it did not resolve, when the same failure happens twice in a row, or any time something appears to do nothing at all. An action that produces no visible result is the failure we most want to hear about, so do not sit on it out of politeness.

1. 01What you were trying to do, in one sentence.
2. 02What happened instead, including any message you saw, word for word.
3. 03Roughly when it happened, with your time zone.
4. 04Which integration was involved, if you know.
5. 05Whether it happened once or every time.
6. 06Never send your API keys, passwords, or a screenshot with a key visible. We never need them, and we will ask you to rotate anything that reaches us by accident.