---
title: "Warnings"
description: "Find the warnings chip and the Dive Warnings dialogue, tell a Warning from an Error, and know which two conditions stop the plan outright."
---

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

# Warnings

import { WarningsDialog } from "@/components/react/ReviewScreens";
import { warningExample } from "@/demo/plans";

Every warning the planner produces lives in one place: a chip in the page
header, labelled with the count (*3 Warnings*, *1 Warning*). It appears only
when there is something to say, and its colour is the worst severity in the set:
amber for Warnings, red if anything is an Error.

Selecting it opens the **Dive Warnings** dialogue, which lists each message in
full. A message belonging to a moment in the dive carries that moment in
parentheses, *(t=42 min)*, so you can find it in the schedule.

That plan is 60 m for 25 minutes on air, with 100 % oxygen breathed from 21 m.
On a clean plan there is no chip, and the dialogue reads *"No warnings, dive
plan looks good!"*

## Warning and Error

The two severities differ in certainty, not in how bad the outcome is.

- **Warning**: the plan is outside a customary limit, and the schedule is
  computed and internally consistent. An ascent rate above the customary figure,
  ppO₂ above the 1.4 bar bottom limit, CNS above the 80 % advisory, OTU above
  200, gas density above the 5.2 g/L advisory.
- **Error**: the planner could not do what was asked, or the plan crosses a hard
  limit. ppO₂ above the absolute 1.6 bar ceiling, CNS above 100 %, OTU above the
  300 single-dive limit, gas density above the 6.2 g/L limit, an
  isobaric-counterdiffusion violation at a gas switch, or a decompression
  obligation that never clears at the current gradient factors and gas.

> **Caution**
>
> An Error does not stop the planner producing a schedule: it computes what it can
> and flags what it could not. A truncated ascent is still drawn, and it is still
> wrong. Read the Error before the runtime.

Most warnings have an input behind them: a rate, a gas, a switch depth, a
gradient factor. Raising a limit to silence one is not available in the planner.
**Ask AI**, beside the chip, opens [Tunang](/assistants/planner), which will
replan the dive with one of those inputs changed. The same severities and limits apply wherever the app judges a gas, as on
[Depth limits](/gases/analysing).

## The two that block the plan

Two conditions stop the **Plan** step advancing to **Review** at all. The
forward control is disabled and states the reason:

- **A closed-circuit plan with no onboard diluent.** *"CCR mode requires an
  Onboard Diluent gas to be configured."*
- **An open-circuit plan with no bottom gas.** *"Open circuit mode requires a
  Bottom Gas to be configured."*

Both are fixed in the [Gas Mixes section](/planning/gas-mixes).

## On a rebreather

The chip carries the loop plan's warnings. A scenario's own objections are not
folded into it: a counterdiffusion warning from its bailout switch is printed
above that scenario's schedule instead. Read both before you commit to a bailout
plan. See [Bailout scenarios](/ccr/bailout).

## Next

[Saving and sharing](/planning/saving-and-sharing), and
[Reference: warnings](/reference/warnings) for the complete catalogue.

Source: https://docs.divelogic.ai/planning/warnings/index.mdx