API indexing retry from Service Module to LLM Module

[matKlju]

AS A Service Administrator
I WANT to manually trigger API endpoint indexing from the Service Module
SO THAT I can recover from failed LLM Module indexing during API endpoint create/edit flows

Description

When an API endpoint is created or edited in the Service Module, the system should attempt to notify/index the endpoint in the LLM Module. If this automatic indexing fails, the user must have a clear way to manually retry the indexing action from the Service Module UI.

Acceptance Criteria

• If LLM Module indexing fails during API endpoint create/edit, the failure is shown to the user as a non-blocking warning.
• API endpoint create/edit must still be saved even if indexing fails.
• Failed indexing state is persisted for the endpoint.
• User can manually trigger “Retry indexing” from the endpoint UI.
• Retry action sends the latest saved endpoint data to the LLM Module indexing endpoint.
• On successful retry:
  • indexing status is updated to success
  • failure warning is cleared
  • last indexed timestamp is updated
• On failed retry:
  • indexing status remains failed
  • user sees a clear error message
  • endpoint data remains unchanged
• Retry indexing must be available for both:
  • global API endpoint modal / API registry
  • canvas-level API endpoint copy, if applicable

Notes

• Indexing failure must not block endpoint creation or editing.
• Use latest saved endpoint data, not unsaved modal state.
• Keep the action explicit; no automatic retry loop required in this task.