Documentation

Tenant OwnerReviewerOperator

Product knowledge base, playbooks, and embedded guidance for every persona.

Retry Behavior in CoffeeBreakAI

CoffeeBreak tries to recover gracefully from temporary or easily fixable problems.
Retry Behavior describes how CoffeeBreak attempts these recoveries and what you can expect as a user.

🔁 When CoffeeBreak Retries

CoffeeBreak automatically retries when issues appear transient:

  • A Git provider or host is temporarily unavailable
  • API requests are rate-limited
  • Network calls time out
  • A pull request or commit operation hits a brief conflict
  • An integration responds with “try again later”
  • The agent marks the issue as recoverable

These situations often resolve quickly on their own.

🚫 When CoffeeBreak Does Not Retry

CoffeeBreak will not retry when the failure is structural or requires human judgment:

  • Task description is invalid or incomplete
  • Generated code fails due to logical errors
  • Merge conflicts require manual resolution
  • Missing or revoked permissions
  • Review is required
  • The system is not confident a retry will help
  • The error is marked non-recoverable

In these cases, the task is paused until someone intervenes.

👤 Human Review Overrides Retries

If a reviewer requests changes:

  • CoffeeBreak immediately stops retrying
  • The system waits for reviewer input
  • Only a human can resume the task
  • Retry attempts reset after approval

See
👉 Human Review & Reviewer Scheduling

🧠 How Many Times Will CoffeeBreak Retry?

Retries follow a safe pattern:

  • A limited number of retry attempts
  • Increasing delay between attempts (exponential backoff)
  • Strict safeguards to prevent runaway loops or provider abuse
  • Auto-fallback to human review when limits are reached

Retry counts and backoff rules are controlled by workspace settings.

📬 UI Indicators

When a retry happens, you may see:

  • A “retrying” banner or activity indicator
  • Delay/backoff message
  • A retry entry in task history
  • An alert if human action is required

Many retries happen quietly and resolve before you ever notice.

⚙ Workspace Controls

Admins may influence retry behavior by configuring:

  • Max retry attempts
  • Backoff strategy
  • Retry severity rules
  • Confidence thresholds
  • Integrations (disconnected integrations will disable retries)

Full configuration options are listed under
👉 Retry Policy

🔒 Safety & Stability

CoffeeBreak’s retry logic ensures:

  • Protection against repeated failures
  • Respect for provider rate limits
  • Avoidance of excessive CI/CD activity
  • Safe fallback to review when uncertain

Retries are always designed to help—never to create noise.