Generation Logs
The Generation Log is where you confirm what happened, what is still running, and why something failed.
The Generation Log Table
Section titled “The Generation Log Table”The full Generation Log is found in the Content > Generation Log sub-tab. It is the main place to monitor all AI activity on your site.
The table provides the following details for every job:
- Status: Current state of the job (Queued, Running, Succeeded, or Failed).
- Source: How the job was triggered (Manual, Bulk, Scheduled, or Transcription).
- Model: Which specific AI model was used for the task.
- Keywords: The topics provided to the AI.
- Created/Runtime: When the job started and how long it took to complete.
- Result: Direct links to “View” or “Edit” the generated post.
The Dashboard Overview
Section titled “The Dashboard Overview”For a quick check, the Dashboard shows the last five generation jobs. This allows you to see at a glance if your recent posts were successful without digging into the full log.
Troubleshooting Failures
Section titled “Troubleshooting Failures”If a job fails, the “Result” column in the full log will display an error message. Common errors include:
- Invalid API Key: Your key may have expired or was entered incorrectly.
- Quota Exceeded: You have run out of credits with your AI provider.
- Network Timeout: The AI provider’s server took too long to respond.
Support: Each failed job includes an “Error” indicator. Hovering over it (on the Dashboard) or checking the Result column (in the full log) will show the specific reason for the failure.
How to use the log operationally
Section titled “How to use the log operationally”- For bloggers: Check that a manual draft actually finished before you start editing it.
- For agencies: Use the source and keyword columns to confirm whether a post came from a client template, a schedule, or a bulk run.
- For technical teams: Failed jobs are the fastest place to see whether the issue is credentials, provider quotas, or prompt/output formatting.