Rotators

Create rotators from saved pools or inline proxies and choose a selection strategy.

Rotators define which proxy sources are available and how the runtime should choose between them.

Rotation Engine Rotators

Rotator Fields

Field	Meaning
Name	Human-readable rotator name.
Notes	Context for the source list or use case.
Tags	Labels such as `rotation`, `pool`, `checked`, or `fallback`.
Sources	Saved pools or inline proxy lists.
Selection strategy	Round robin, random, or least recently used.
Policy	Runtime behavior attached to the rotator.

Source	Use when
Saved pool	You want durable, reusable, tagged source material.
Inline proxies	You need a quick temporary source that does not belong in a pool yet.

Field	Detail
ID	Stable local rotator identifier.
Name	Human-readable label in lists and runtime snapshots.
Notes	Context for source quality, target use, or operational intent.
Tags	Labels such as `rotation`, `checked`, `pool`, `fallback`, or country hints.
Sources	Pool-backed sources and inline direct proxy list sources.
Selection strategy	Round robin, random, or least recently used.
Policy ID	Policy that controls sessions, health, fallback, and penalties.
Timestamps	Created and updated timestamps for workspace memory.

Legacy primary/fallback pool fields are migrated into source records, and source IDs/names are normalized.

Strategy	Behavior
Round robin	Walk through available proxies in order.
Random	Choose available proxies randomly.
Least recently used	Prefer proxies that have waited longest since last selection.

A rotator can only be as good as its sources. Use pools that have been:

Use pool sources for long-lived rotators. Inline sources are better for tests or temporary experiments.