OpenAI test reports authentication, quota, or service errors.
Where to Check in PassiveWP
WordPress Admin -> PassiveWP -> Settings -> OpenAI
Step-by-Step Fix Walkthrough
Fix Step 1: Regenerate API key and update settings.
Where to click WordPress Admin→PassiveWP→Settings→OpenAI
What to do In WordPress Admin→PassiveWP→Settings→OpenAI, paste your key into "OpenAI API Key", click Save Changes, and stay on the page until the success notice appears.
How to verify No blocking error banner appears, and the next step is available.
Fix Step 2: Check billing/quota in OpenAI dashboard.
Where to click WordPress Admin→PassiveWP→Settings→OpenAI
What to do Use WordPress Admin→PassiveWP→Settings→OpenAI to run generation for one item first, review the output manually, then continue with the remaining items.
How to verify Generation should complete without authentication, quota, or model errors.
Fix Step 3: Retry using a supported model configuration.
Where to click WordPress Admin→PassiveWP→Settings→OpenAI
What to do In WordPress Admin→PassiveWP→Settings→OpenAI, do this in order: open the relevant panel, find the control related to "Retry using a supported model configuration.", apply one change, click Save/Run, then reload once to confirm it stuck.
How to verify No blocking error banner appears, and the next step is available.
Fix Step 4: Wait and retry for temporary service instability.
Where to click WordPress Admin→PassiveWP→Settings→OpenAI
What to do Use WordPress Admin→PassiveWP→Settings→OpenAI to run generation for one item first, review the output manually, then continue with the remaining items.
How to verify Generation should complete without authentication, quota, or model errors.
Most Common Causes
- Invalid API key.
- Billing/quota restrictions in OpenAI account.
- Temporary model or service availability issues.
How to Prevent It Next Time
- Rotate keys with documented process.
- Set spend limits and monitor usage weekly.
- Keep fallback model choices ready.
When to Contact Support
- You completed every fix step and still get the same error.
- The issue impacts revenue-critical pages or high-volume campaigns.
- You can share timestamps, affected link/product IDs, and screenshots of the exact error state.
