Skip to content

Batches and conflicts

A batch can contain one or more profile runs. This lets Brokerr reuse source data when several profiles use the same configured source.

Profiles using the same source share a scan. Different providers may run in parallel, while requests to the same provider are paced to avoid rate limits. Queued batches are shown in Dashboard and Runs.

Each profile keeps its own metrics, errors, and diff entries. One failed profile does not stop unrelated profiles in the same batch.

If profiles request different changes for the same target item, Brokerr does not write either change. Both profile tabs show a conflict that must be resolved.