Profile Grouping with Priority-Based Rotation on Failure

[deyil]

Summary:
Introduce “Profile Groups” that let users assign an ordered list of profiles to a mode. Profiles are tried strictly by user-defined priority for the current request only. If a profile fails during a request, the system immediately tries the next profile in order for that same request. On the next new request, selection starts again from the top of the priority list.

Problem:

• Modes tied to a single profile require manual intervention on failures.
• Reusing fallback logic across modes is cumbersome.
• Users want deterministic, priority-based fallbacks without persistent rotation state.

Proposed Solution:

• Add Profile Groups: an ordered list where position defines strict priority.
• Assign a Profile Group to a mode instead of a single profile.
• Execution flow:
  • For each request, start with the first profile in the group.
  • If the current profile errors or times out, immediately try the next profile in order for that same request.
  • If all profiles fail, return the final error with an attempt trace.
• Rotation resets per request: every new request begins at the top-priority profile, regardless of previous failures.

Key Details:

• Rotation behavior: strictly priority-based, per-request. No round-robin, no persistent state.
• Retry policy: configurable max attempts and per-profile timeout. Optional backoff between profile switches.
• Observability: log which profile was used, how many fallbacks occurred within the request, and error summaries.
• Configuration UX:
  • Create Group: name, description, ordered profile list, default timeouts and max attempts.
  • Assign Group to Mode: select group instead of a single profile.
  • Optional mode-level overrides for timeouts and max attempts.

Benefits:

• Resilience: automatic per-request fallback without manual switching.
• Predictability: deterministic priority order chosen by the user.
• Simplicity: reusable groups across modes reduce duplication.
• Maintainability: updating a group updates all associated modes.

Acceptance Criteria:

• Users can create, edit, and delete Profile Groups with an ordered profile list.
• Modes can reference a Profile Group in place of a single profile.
• For each request, the system attempts profiles in order until success or exhaustion, then resets order for the next request.
• Configurable per-profile timeout and max attempts at group and mode level.
• Logs/metrics expose profile selection, within-request fallbacks, and attempt counts.

Non-Goals:

• No failure trigger configuration.
• No load-based or round-robin rotation.
• No dynamic reprioritization based on performance.

Migration:

• Existing modes retain current profile settings.
• Users can introduce groups and switch modes to them incrementally without downtime.