---
title: "Scrubber tracking"
description: "Enter a rated scrubber duration and read the two warnings and the overtime error the planner raises against the dive's runtime."
---

> 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.

# Scrubber tracking

import { ScrubberCard } from "@/components/react/PlannerSettingsScreens";

Scrubber tracking compares the dive's runtime against a rated CO₂ scrubber
duration you supply, and raises warnings as the runtime approaches it. It is
advisory: the schedule is never altered. A plan with tracking on and the same
plan with it off produce the same stops, the same runtime and the same time to
surface.

## Entering a duration

The field is **Scrubber Duration**, in minutes, on the **Scrubber** card in
**Plan → CCR**. It accepts whole minutes from 1 upwards.

Leave it empty and tracking is off. A value that is not a positive number is
also treated as off, and the planner says so:
`Scrubber duration 0 min is not positive; scrubber tracking disabled`.

## The three thresholds

| Condition | Severity | What you see |
|---|---|---|
| Runtime enters the final 60 minutes of scrubber life | Warning | `Scrubber within 60 min of its 180 min rated duration` |
| Runtime enters the final 30 minutes | Warning | `Scrubber within 30 min of its 180 min rated duration` |
| Runtime exceeds the rated duration | Error | `Scrubber rated duration 180 min exceeded by 12 min at surfacing` |

Each warning carries the minute of the dive at which it triggers, so they land
on the timeline rather than at the end. The overtime error is raised against
surfacing, because that is where the total is known. All three appear in the
Dive Warnings modal alongside the rest, listed in
[Warnings](/planning/warnings).

## What it does not do

The rated duration is treated as a fixed budget of minutes. Nothing else about
the dive enters the comparison: not water temperature, not depth, not work rate,
not how long the scrubber has already been used, not CO₂ readings from the unit.

> **Caution**
>
> An **Error**-severity scrubber warning does not stop the plan being computed,
> saved or dived. The planner reports; it does not refuse. Equally, the absence of
> a scrubber warning means only that the runtime fits inside the number you typed.

## Next

- [The Review step](/planning/reviewing) is where a finished plan is read, and
  the next step of the walkthrough.
- [Warnings](/planning/warnings) shows where these three land and how severity
  is used across the planner.

Source: https://docs.divelogic.ai/ccr/scrubber/index.mdx