Help Center / Monitoring & Clipping HealthMonitoring

Know what Cliprr is doing at a glance.

Clipping Health is designed to tell you whether automatic clipping is operating normally, temporarily limited, or needs attention—without filling the Monitor page with debug noise.

Clipping Health

A quick read on whether automatic clipping can accept new work.

The Monitor page keeps health information compact until you need it. Expand Details for queue activity, rate limiting, pending jobs, and other telemetry.

Clipping HealthHealthyDetails ▾

Healthy uses a subtle status indicator instead of a large debug panel. Detailed controls and telemetry stay out of the way until expanded.

Healthy

Cliprr is operating normally and can accept/process new automatic clips under the current conditions.

Limited

Cliprr may temporarily slow or limit new automatic clipping because of queue, rate, or resource conditions.

Attention Needed

Something is preventing normal clipping and may require a user action or a closer look at Details.

Queue activity

A growing queue does not automatically mean failure. Heavy work can be serialized or delayed by resource protection, and long-form/short-form jobs can compete for the same protected processing capacity.

Rate limiting

Cliprr can temporarily limit new work when safety or provider rate controls are active. Check Details before repeatedly restarting the monitor.

Pending and active jobs

Pending jobs are waiting; active jobs are currently being processed. If one job is heavy, later work can wait until capacity is available.

Pause / Resume automatic clipping

Pause/Resume belongs inside the expanded health details so you can intentionally stop automatic clipping without confusing that control with a permanent error state.

When “Limited” persists

Check resources and the queue before restarting everything.

If Cliprr is waiting because another heavy job is active or system memory is low, the safest behavior is often to let the current work finish.