get_generation_status

​

Arguments

​

Returns

{
  "content_id": "7f5e2c1a-...",
  "output_type": "release_notes_email",
  "status": "completed",
  "error_message": null,
  "skip_reason": null,
  "review_status": "ready_for_review",
  "is_published": false,
  "published_at": null,
  "public_slug": null,
  "created_at": "2026-08-10T14:02:11+00:00"
}

• status is the generation state: pending → processing → completed, or failed (with the failure reason in error_message).
• skip_reason is "no_customer_facing_changes" when a single-feature run (X thread, LinkedIn post, feature page, banner) found nothing customer-facing in the period and declined to post: status is failed, error_message reads “nothing to post”, nothing was published, and the credits were refunded. Don’t retry as-is — widen the date range, or pass instructions such as “do announce docs-site changes” if that change should count. null otherwise.
• review_status is the publication state of the associated review event, when one exists: ready_for_review, approved, published, or skipped (also the state of a scheduled occurrence the generator declined). It is null for records with no review event.

​

Errors

• Invalid content_id (must be a UUID): abc123
• Content not found: 7f5e2c1a-... — no record with that ID exists in this project.

​

Example prompts

“Is the changelog I kicked off done yet?”

“Check the status of content 7f5e2c1a and tell me if it failed.”