Recurring batches configuration

What the Screen Is For

Administrators define successive intake collections here and inspect whether scheduled rolling has completed. Stream activity controls future occurrences rather than directly changing the current collection eligibility.

What It Shows and Lets People Do

The collection can be narrowed by business unit, activity and search. The editor combines naming templates with schedule controls and previews. Saving active configuration attempts its first collection, while run history explains later occurrence outcomes and predecessor posting preparation. Delete uses a confirmation dialog and dependency refusal handling.

States and Errors

Version conflicts require a fresh read. In-use streams cannot be removed, and the deletion dialog retains the service explanation. The adapter and editor omit both response-only first-batch refusal and schedule pause reason; this contract therefore makes no claim those recovery explanations are visible.

Patterns It Must Respect

The list uses standard PageLayout width and the editor full width. Template examples, schedule preview, outcome badges and destructive confirmation are the observed patterns.