Reference

Troubleshooting

WordPress authentication failures are the most common integration issue. Verify that your Application Password was generated for the correct user and that the user has the Editor or Administrator role. If you are using a security plugin like Wordfence or iThemes Security, whitelist the InkieAI IP range 34.120.0.0/16 in your firewall rules. Check the Run Logs panel for the exact HTTP status code returned by WordPress.

Webhook timeouts usually indicate a slow or unreachable endpoint. Ensure your server responds within 10 seconds and returns a 2xx status. If you are behind Cloudflare, verify that the InkieAI user agent is not being challenged. For Vercel deployments, consider increasing the maxDuration of your API route or moving heavy processing to a background job.

Articles stuck in publishing mean the generation succeeded but the push to your CMS or webhook failed. Open the article detail view and click Retry Publish. If the issue persists, check whether your CMS credentials or webhook URL have changed recently. Run Logs retain the last 30 days of execution history with full request payloads, response bodies, and stack traces for failed steps.

Errors that start with AI_APICallError or mention Azure/OpenAI response schemas happen during InkieAI article generation, before your Next.js, WordPress, Ghost, or webhook integration is called. They are not caused by customer-side install snippets. Retry the run after updating InkieAI; if it repeats, contact support with the run ID so we can inspect the AI provider response-format schema.