DEV SIGN-IN. Government of Maharashtra interoperability operations. This is a labelled demonstration - API calls carry a bearer token from the local dev Keycloak, not production SSO.

समन्वय SAMANVAY State operations

Government of Maharashtra · Interoperability middle layer. Exceptions and recovery.

Incident

Beat 4 is one story from live queues: a killed data source, apps in PARTIALLY_VERIFIED, open exceptions, then revive and one-click Retry. Kill/revive POSTs exist only on the demo profile. Default boot 404s them.

Boot with --spring.profiles.active=demo for chaos. Without it, GET and POST /api/connector/chaos/* stay unregistered. Kill asks for confirmation. Chaos needs a staff token with OFFICER or ADMIN (dev Keycloak).
  1. 4 Kill connector, start from Caller, see PARTIALLY_VERIFIED + exception
  2. 4 Revive, then one-click Retry
  3. 5 Consent revoke appears as GRANT_DENIED

Reading live queues…

Recovery

  1. Degraded
  2. Revive
  3. Retry
  4. Recovered

Load the queues to compose the story from live rows.

Affected connector

Live kill state from GET /api/connector/chaos/{dataSourceCode} (demo profile). Catalog supplies the data-source code. Seeded health_status is not shown.

    Impacted apps

    Rows in PARTIALLY_VERIFIED from /api/applications.

    Open exceptions

    From /api/journeys/exceptions. Retry posts to /api/journeys/instances/{id}/retry on that row. No UUID paste.

    Demo chaos (Kill / Revive)

    Secondary drill. These POSTs exist only on the demo profile. Killing a connector is destructive to in-flight fetches. Default boot 404s them.

    Loading connectors…

    Consent denials (GRANT_DENIED)

    Technical detail