Skip to main content
Most Generatify problems fall into one of three groups: a feature that needs a provider and does not have one, a request that takes longer than your host allows, or a free feature behaving differently from how people expect because it runs in the browser.

​
Start here

1

Check whether the feature needs a provider

The copilot, content generation, meta descriptions, and helpdesk conversation mode all call an AI provider. Everything else does not. See free and Pro.
2

Check the model selector

Go to Generatify > Chatbot. If it reads No AI Model Available, no connector is enabled or no key is saved, and every provider-backed feature will fail.
3

Check the provider dashboard

Out of credit, rate limited, and revoked key all look identical from inside WordPress. The provider will tell you which.
4

Check your browser console

The free features run client-side. If alt text, toxicity checking, smart compose, or the page agent is not working, the error is in the console, not in PHP.

​
Common problems

The connector toggle itself has to be on, not just the key filled in. Check the toggle above the key field on Settings > Connectors, and save again.
Almost always your host’s PHP execution limit rather than the provider. A long article can take a minute or more, and shared hosting often cuts requests off at 30 or 60 seconds.Raise the limit at the host if you can. If you cannot, generate content in parts: title and body separately, then tags and the featured image afterwards. See the timeout filters.
Conversation mode needs Pro and a connected provider. The endpoint that answers messages is only registered on a licensed install, so a free site falls back to the form.
Only empty alt attributes are filled, so images you already described are skipped by design. The model also runs in the browser, so check the console for a failed model load, particularly on sites with a strict content security policy.
The check runs in the commenter’s browser before submission. Anything that posts directly to wp-comments-post.php never runs it. This is a usability feature, not spam protection, and it does not replace your existing spam plugin.It also only detects English, and only the categories it was trained on. Spam, off-topic comments, and politely worded bad faith all pass.
The page agent defaults to bottom-left and the helpdesk agent to bottom-right precisely to avoid this. If you moved one, move it back, or disable whichever you use less. Also check for a chat widget or cookie banner claiming the same corner.
They only register in a browser that supports WebMCP, which is currently a small set. In any other browser this is expected, not a fault. Confirm the routes themselves work by calling one directly:
History is kept in your browser’s local storage, not in your database. It does not follow you to another browser or machine, and clearing site data clears it.
Changes are held until confirmed. If you did not confirm, nothing was written. Ask it to list pending changes.
Check DISALLOW_FILE_MODS and DISALLOW_FILE_EDIT in wp-config.php. Both are honored. Then check the extension is on the allowlist and the path is inside wp-content.

​
Unexpected provider costs

DaftPlug cannot see or cap your provider usage. If a bill surprises you, the provider’s dashboard is the only place that shows what caused it.
The two usual causes:
  • Helpdesk conversation mode on a busy site. Your visitors control how often this runs, not you.
  • Long copilot conversations. Every message resends the whole conversation, so cost climbs as the chat grows. Start a new chat when you change subject.
Set a spending limit in the provider dashboard. It is the only hard ceiling that exists.

​
Conflicts worth knowing about

Still stuck

What to include when you contact support.