Skip to main content

​
Generation Issues

The submission was refused before a workflow started. Studio shows the field or admission reason returned with HTTP 422. Correct the brief, replace an incomplete source if required, or select a permitted template/style combination, then submit again. This rejection creates no workflow or draft and charges no generation credit.
The chosen length takes longer to write than that tier’s time budget allows. Choose the tier Studio offers, which shows its credit cost, or pick a shorter length. Nothing is charged for a refused request. See Length decides the tier.
Contexts such as Healthcare Legal & Compliance require a minimum number of cited sources. When research finds fewer, the run stops before any draft is written, says how many it found against how many are required, and is refunded. Searches use the subject of your topic, so lead with what the document is about (for example “Governance policy for AI-assisted radiology triage”) and put your organization’s situation after it. Adding reference documents to your workspace library also counts toward the minimum.
Runtime depends on tier, research, requested length, and provider response. Workflow timeouts are 180 seconds for Quick, 630 seconds for Standard, and 900 seconds for Premium. Before resubmitting:
  • Refresh the page and check your Content Library — the generation may have completed in the background
  • If the issue persists, contact support with your request ID when available
Review the brief, evidence, template, and style together:
  • Is the topic specific enough? Vague topics produce vague output.
  • Is the audience defined precisely? “Developers” is less useful than “senior backend engineers evaluating vector database options.”
  • Is the style profile appropriate for the template and audience?
  • Did you provide key points? They help shape the structure and direction of the draft.
If inputs are solid and quality is still poor, try section regeneration on the weak sections before re-running the full generation.
Accepted runs that fail follow the credit-refund path. Studio names the stage the run stopped in and the reason: a time limit (with the tier’s budget), too few sources, a check that rejected the draft, citations that could not be verified, or an internal error. If a generation fails:
  • Review your input fields. Missing required fields or malformed values can cause failures.
  • Check the failed stage and diagnostic before retrying. A provider request error can occur after valid planning and research; changing the topic will not repair incompatible provider settings.
  • If the same generation fails repeatedly, contact support@writerzroom.com with the request ID
The planner recovers recognized response envelopes and missing key messages when a valid strategy is already present. Other schema failures remain errors, classified as invalid output rather than provider access. A schema error alone does not establish an outage or invalid credentials. See Model Routing for stage-specific routes and Reliability and Generation Failures for execution recovery.

​
Publishing Issues

Check the connection in Integrations, the owner of publishing destinations. Settings’ publishing link also opens Integrations. Confirm the required credentials and destination settings, then retry delivery.
This is usually a platform-side delay. Some platforms can take time to index new posts. Check the platform directly. If the post does not appear after 5 minutes, check the post status. It may have been saved as a draft rather than published.
WriterzRoom creates the newsletter issue in Beehiiv but does not trigger the send. Log in to Beehiiv and send the issue from there. WriterzRoom is not able to initiate Beehiiv sends.

​
Account and Billing Issues

Dashboard usage counts can take up to 15 minutes to refresh after a billing cycle reset. Hard refresh your browser (Ctrl+Shift+R / Cmd+Shift+R) and check again.
Contact support at support@writerzroom.com with your account email, the date of the charge, and any billing confirmation you received.

​
API Issues

Your API key is missing, malformed, or expired. Confirm you’re sending Authorization: Bearer YOUR_API_KEY in the request header. If the key looks correct, regenerate it in Settings → API Access.
You’ve hit the rate limit. Reduce request frequency and implement exponential backoff in your client.
Poll the status endpoint every 5–10 seconds. If status remains processing beyond the expected processing window, record the request_id and contact support.
Last modified on October 20, 2026