Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Indexer Schedule Controls UI

  • Status: Accepted
  • Date: 2026-03-15
  • Context:
    • The indexer admin console already exposed rate-limit assignment, but the ERD parity checklist still had per-indexer schedule controls in UI unchecked.
    • The API already accepted is_enabled, enable_rss, enable_automatic_search, and enable_interactive_search through the existing indexer instance update endpoint.
    • AGENTS.md requires completing the next efficient ERD-backed slice without adding dead code or extra dependencies.
  • Decision:
    • Extend the /indexers admin console to surface explicit checkbox controls for instance enablement, RSS, automatic search, and interactive search scheduling.
    • Reuse the existing IndexerInstanceUpdateRequest payload instead of introducing a separate UI-only endpoint or new backend model.
    • Lock the route behavior in Playwright by asserting the schedule controls render on the page.
    • Alternatives considered: delaying the controls until broader instance list/read APIs existed, or adding a dedicated scheduling sub-view. Both would have left an already-supported ERD path hidden from operators.
  • Consequences:
    • Positive outcomes:
      • Operators can now control the ERD-backed per-instance scheduling flags directly from the admin console alongside rate-limit assignment.
      • The checklist item for per-indexer rate limits and schedule controls now has matching UI coverage and browser verification.
      • No new dependencies were added.
    • Risks or trade-offs:
      • The update action still targets a manually entered instance UUID because list/read endpoints for all instances are not yet available in the UI.
      • Schedule state is operator-driven rather than auto-refreshed from the server after each mutation.
  • Follow-up:
    • Implementation tasks:
      • Add richer instance selectors and readback once list/read instance endpoints are available in the UI.
      • Expand the console further for RSS history and mark-seen workflows when those reads are exposed.
    • Review checkpoints:
      • Keep just ci and just ui-e2e green.
      • Revisit the remaining unchecked parity items around app sync, health visibility, RSS views, connectivity dashboards, backup/restore, and final migration acceptance.