Setup Needs Attention #
If Overview displays a setup error, the plugin’s required database structures were not installed or verified. Generation intentionally stops because usage, tokens, rate limits, or image sessions could not be handled safely.
Confirm the database user can create and alter WordPress plugin tables, reactivate the plugin on a staging copy, and review the exact error and WordPress debug log. Do not manually mark a schema version current without confirming the tables and columns exist.
Database Read Or Write Failures #
Rate-limit, usage-ledger, token, lock, and image-session writes fail closed where they protect a request. Check database availability, permissions, table health, disk space, and query errors.
Provider Timeout #
Synchronous and frontend requests use shorter timeouts to avoid holding a visitor request indefinitely. Async and workflow paths have a longer wall-clock allowance. A timeout can occur after a provider began processing, so consult provider usage before assuming no billable work occurred.
Reduce output length or image cost, use Async text execution where appropriate, and investigate server egress/network performance. Developers can review timeout constants in Developer Reference.
Cleanup Problems #
The plugin schedules cleanup for expired tokens, rate-limit state, locks, and temporary image sessions. Confirm WordPress cron runs reliably. On a low-traffic site, configure a real cron runner for WordPress scheduled events according to hosting guidance.
When asking for support, provide plugin versions, plan, form/feed IDs, timestamps, sanitized error messages, and relevant logs. Never provide API keys, encryption keys, WordPress salts, or database credentials.
