> ## Documentation Index
> Fetch the complete documentation index at: https://docs.writerzroom.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reliability and Generation Failures

> How to interpret failed generations and what to do when a request does not complete.

WriterzRoom generation is asynchronous. A request is submitted first, then processed through visible stages until it completes or fails.

A request may remain in progress for a meaningful period before the final state is available.

## Reliability Overview

<div style={{ display: 'grid', gridTemplateColumns: 'repeat(4, 1fr)', gap: '12px', margin: '1.5rem 0' }}>
  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>Async Processing</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Requests move through visible generation stages.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>Clear Failures</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Failed jobs return an error instead of degraded output.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>No Credit Charge</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Failed generations are not intended to consume credits.</div>
  </div>

  <div style={{ border: '1px solid rgba(128,128,128,0.20)', borderRadius: '14px', padding: '16px', background: 'rgba(255,255,255,0.04)' }}>
    <div style={{ fontWeight: 800 }}>Recovery Path</div>
    <div style={{ fontSize: '13px', color: 'var(--colors-content-secondary)' }}>Review inputs, confirm status, then retry once with cleaner parameters.</div>
  </div>
</div>

## Normal Generation Behavior

Generation runs through a staged pipeline. Depending on tier and template, a request may take longer when research, editing, SEO, formatting, or publishing preparation is involved.

A request that appears active may still be processing.

## When a Failure Happens

A failed generation does not automatically mean the platform is unavailable.

In many cases, the issue is limited to:

* A specific request
* An input combination
* A temporary service delay
* A validation failure
* A plan-related constraint
* A tier mismatch with requested length or complexity

## What to Check First

<Steps>
  <Step title="Confirm status">
    Check whether the request is still processing before treating it as failed.
  </Step>

  <Step title="Review template and style selection">
    Confirm that the selected combination matches the intended output.
  </Step>

  <Step title="Check required inputs">
    Make sure all required fields are complete and specific.
  </Step>

  <Step title="Assess tier fit">
    Confirm the selected tier has enough capacity for the requested output length or complexity.
  </Step>

  <Step title="Retry once with cleaner inputs">
    If needed, retry with more specific and simplified parameters.
  </Step>
</Steps>

## Good Recovery Pattern

Do not immediately resubmit the same request multiple times.

First review the inputs, confirm status, and then retry once with cleaner or more specific parameters if needed.

<Tip>
  If a request fails repeatedly with clean inputs, capture the request identifier before contacting support.
</Tip>

## Credits and Failed Generations

Failed generations are not intended to consume credits.

If a generation fails before completion, your credit balance should not be charged. If you notice a mismatch, contact support with the request identifier.

## When to Contact Support

Contact [support@writerzroom.com](mailto:support@writerzroom.com) when:

* A request remains stuck beyond a reasonable processing window
* Multiple clean attempts fail
* The issue blocks an active workflow
* You need help investigating a specific request

Include the request identifier when available.