Troubleshoot Automations

A run is waiting for a WordPress slot

Waiting for slot normally means the article is prepared and scheduled for the next available posting time.

Open the run and check its go-live time. If no useful slot is available:

1. Open Project Settings.
2. Confirm that posting time slots exist.
3. Confirm that the automation uses the intended WordPress author or project-default schedule.
4. Add or adjust future slots.

Runs cannot publish without a free slot.

The article published, but Facebook did not

Open the automation and check for the warning No Facebook pages connected.

Then confirm:

• Strevio is connected in Project Settings.
• At least one Facebook page is selected in the automation's Setup step.
• The expected pages are available to the connected Strevio account.
• The run details show a Facebook queue item for each target page.

A Facebook reach automation with no selected pages still publishes to WordPress, but skips the Facebook queue.

Competitor topics are missing or irrelevant

Edit the automation and check the Research step:

• Select the intended Strevio competitor list.
• Make sure the list contains active, relevant pages.
• Increase the research look-back window if there is too little source material.
• Remove an overly narrow filter term or post-type filter.
• Lower the engagement gate if very few posts clear it.
• Choose Propose from research & playbook when the pool runs dry if you want the pipeline to continue.

Without a competitor list, topic research is freeform rather than based on proven competitor posts.

Site traffic topics are empty

Confirm that Plausible is connected and collecting data for the project. Then verify that the automation targets a channel that has traffic: Google, NewsBreak, or both.

New or low-traffic sites may not yet have enough winning pages to mine. Use Run now with a custom topic while more traffic data accumulates.

A run failed

Open the failed run and read the reason shown on the page. Select Logs for the detailed execution history.

Common causes include:

• WordPress, Strevio, or Plausible credentials are missing, expired, or lack permission.
• The WordPress site is unreachable.
• No posting slot is available.
• The credit balance is too low.
• A source image cannot be downloaded or processed.
• The research source returned too little usable material.

Fix the underlying cause, then select Retry. Retry reuses completed work when possible: a saved article or existing WordPress post may be resumed instead of recreated.

A running job with no recorded progress for more than 15 minutes is treated as stuck and becomes retryable.

Autopilot paused itself

Autopilot pauses after three consecutive failed runs since its last edit or reactivation. This prevents repeated failures from consuming more time or creating bad output.

1. Open the latest failed run.
2. Read the reason and logs.
3. Fix the connection, schedule, credits, or content setting.
4. Retry one run if appropriate.
5. Select Resume after the test succeeds.

The first run cannot start

Check the warning strip in the automation editor:

• Connect WordPress when the project has no usable WordPress credentials.
• Set the schedule when no posting slots exist.
• Connect Strevio when Facebook publishing or competitor research is expected.
• Review usage when the available balance is below the estimated first-run cost.

The Run now button is disabled while an automation is paused. Resume it after resolving the warning.

The wrong content or image keeps appearing

Pause the automation before making broad changes.

Then review:

• The region and research filters.
• Enabled article types and their mix.
• Shared instructions and per-type overrides.
• Image source, selection strategy, template, and style.
• Caption mode and approved caption learnings.
• Project-wide learnings that may also affect this automation.

Test the change with one Manual run before returning to Autopilot.

Before contacting support

Collect:

• The project and automation name.
• The run title and time.
• The run status and full error reason.
• Whether WordPress, Facebook, or both were affected.
• The run logs.
• Any recent changes to credentials, schedules, prompts, article types, or destinations.

This information identifies the failed pipeline stage and makes the issue faster to reproduce.