Start with the message shown in the AI screen. A license problem, an exhausted allowance, and a rejected provider key need different fixes.
Choose the matching problem
| What you see | What to check |
|---|---|
| License activation requested or license rejected | Activate the correct license on this website. Check the website activation and plan status, then reopen the AI flow. |
| Included AI credits are exhausted | Review your credit allowance. Eligible licenses can connect their own provider; other plans show an upgrade option. |
| Connect your AI provider | Select the provider that issued your key and complete provider setup. A chat-app password or Noptin license key is not a provider API key. |
| The stored API key was rejected | Click Update API key when offered, or open API Settings. Check the provider, key validity, API access, and account quota. |
| The AI service is temporarily unavailable | Wait and try again. If the problem continues, contact support. Do not repeatedly submit the same request while an earlier attempt may still be running. |
| Failed to fetch or unable to load AI access | Check that the browser and website can reach the service. Check browser/network blocking and retry after the connection is restored. |
| A task is marked Needs attention | Read that task’s message. Check missing settings, integrations, permissions, or invalid values before trying again. |
Check for saved results before retrying
A request can create one item and fail on a later step. Open Noptin → Emails or Noptin → Automation Rules and look for the result before submitting the same request again. Otherwise, you may create duplicates.
Open any saved item and check its status. A failed generation message does not prove that nothing was saved or that every saved automation is inactive. Make unintended active workflows inactive while you investigate.
Use Retry when offered after you have addressed the problem. For a bad provider key, use Update API key instead. Earlier successful AI processing may have used credits even if a later step failed.
Check your provider connection
- Confirm that the provider selected in Noptin matches the key. For example, an Anthropic key must use Anthropic (Claude).
- Confirm the key has not expired or been revoked, and the provider account can make API requests.
- Check the provider’s API usage, quota, billing, and service status. A key can save successfully but fail when generation begins.
- If you replaced or removed a key, reopen the AI screen and verify the current setup. Configure each website separately.
If the screen does not show provider settings, check when the connection form is available. Included credits take priority over a personal provider key.
Improve an unexpected result
Give a smaller, concrete request. Name the audience or triggering event, the intended action, exact URLs and values, and any required delay or condition. Check the result using the email review steps or the automation review steps.
If a reference image is rejected, use JPG, PNG, or WebP and keep it at 5 MB or smaller. Replace placeholders in the generated email before sending.
Separate generation from email delivery
If the email exists but a test or campaign does not arrive, AI generation has already finished. Follow How to Fix Emails Not Sending and inspect Noptin’s Debug Log for delivery errors. Adding AI credits does not repair your mail configuration.
What to send to support
Contact Noptin support with the exact error, the page or task where it appeared, the approximate time, your Noptin version, the affected website, and a short description of what you requested. Include a screenshot and a request ID if one is available. Explain whether an email or rule was created before the failure.
Remove API keys, license keys, subscriber details, and other private information from screenshots and copied messages. Support does not need your full provider key to identify a generation error.
Leave a Reply