My API key is saved, but generation fails
  1. Read the exact error and note the selected provider. “Saved” only means the credential is stored.
  2. Check that provider account's billing, quota, model/feature access, and key restrictions using the links shown in the error. A 400 may be request/model format, not a bad key.
  3. For missing AI response fields, use Retry failed fields only if the valid draft and source still match. Explicit repair can cost another request; at most two repairs are available within ten minutes.
  4. For a timeout or uncertain completion, refresh/check the saved result before retrying to avoid duplicate charges. Record the error without sharing the key.

Confirm: one intentional request completes and its reviewed result is saved.

The YouTube thumbnail is old

Open the affected sermon and confirm the saved YouTube video is the right one. Choose Refresh from YouTube under Featured image. If YouTube still serves the same image, wait for its update; a WordPress refresh cannot create the custom image on YouTube. Preserve custom-image choices and review any replacement confirmation. Purge page/CDN caches after a confirmed update.

Confirm: the editor and signed-out sermon card show the intended image.

Automatic imports stopped, are paused, or never ran

Check imports are enabled, the connected channel, start date, Shorts policy, exclusion rules, queue, and the specific result message. Upcoming/live or nonpublic recordings may not be eligible. Check now runs with live progress and needs the tab open; saved background work needs WordPress cron traffic or a host cron. Let the current worker finish before starting another check. Do not manually delete worker locks.

Confirm: the last check advances and each queued item has a result or an explained retry time.

The homepage or some rows are empty

Check Theme Setup says Grace is your homepage; select the App layout if you expect media rows. Check row visibility/order and publish eligible sermons. Continue Listening needs that browser's history. Distinct For You recommendations may hide when none remain. New sites do not need a demo import to fix missing content.

Confirm: an eligible public sermon appears in Recent Sermons while signed out.

The contact form says sent, but nothing arrives

Verify Send Messages To under Contact Info; blank uses the WordPress administration email. Check spam and your host/SMTP delivery logs. “Accepted for sending” does not guarantee inbox arrival. Configure authenticated outgoing mail with your host or a mail plugin, then send an authorized real test. Avoid publishing diagnostic logs or visitors' messages.

Confirm: the intended inbox receives the test and Reply-To points to the test sender.

Changes save, but the public page looks unchanged

Confirm the correct Save All Options, Update, or Publish action completed. Check that you edited the intended page/layout, then purge the page plugin, host, and CDN caches that apply. Refresh a signed-out browser. Do not cache signed-in, preview, or password-protected pages, or block WordPress form/AJAX endpoints.

A video or audio player will not play

Check the saved media source and its precedence, public visibility/embedding permission, HTTPS, and the direct URL. MP4 needs compatible H.264/AAC encoding, fast-start, byte-range serving, and correct CORS when remote. The theme does not transcode media. Test a signed-out page on the actual device.

A critical error, missing menu, or 404 appears

For missing church content menus, confirm Core is active. After a slug/rewrite change, an administrator can save Settings → Permalinks once. For a critical error use WordPress Recovery Mode and private host error logs, recording the file/line and component versions. Investigate implicated components on staging; do not reset the live site or expose logs publicly.