Strategy job errors out or never completes.
Where to Check in PassiveWP
WordPress Admin -> PassiveWP
Step-by-Step Fix Walkthrough
Fix Step 1: Verify OpenAI connectivity first.
Go here WordPress Admin→PassiveWP
Do this Use WordPress Admin→PassiveWP to run generation for one item first, review the output manually, then continue with the remaining items.
Confirm Generation should complete without authentication, quota, or model errors.
Fix Step 2: Narrow strategy scope to one niche segment.
Go here WordPress Admin→PassiveWP
Do this In WordPress Admin→PassiveWP, do this in order: open the relevant panel, find the control related to "Narrow strategy scope to one niche segment.", apply one change, click Save/Run, then reload once to confirm it stuck.
Confirm No blocking error banner appears, and the next step is available.
Fix Step 3: Reduce concurrent jobs and rerun.
Go here WordPress Admin→PassiveWP
Do this In WordPress Admin→PassiveWP, do this in order: open the relevant panel, find the control related to "Reduce concurrent jobs and rerun.", apply one change, click Save/Run, then reload once to confirm it stuck.
Confirm No blocking error banner appears, and the next step is available.
Fix Step 4: Break large strategy requests into phases.
Go here WordPress Admin→PassiveWP
Do this In WordPress Admin→PassiveWP, do this in order: open the relevant panel, find the control related to "Break large strategy requests into phases.", apply one change, click Save/Run, then reload once to confirm it stuck.
Confirm No blocking error banner appears, and the next step is available.
Most Common Causes
- AI service connectivity or quota issues.
- Input scope too broad and heavy.
- Queue congestion from overlapping jobs.
How to Prevent It Next Time
- Use phased planning for big niches.
- Keep generation windows outside peak operations.
- Monitor queue load before new runs.
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.

