Entitlement API and UI mismatch in ISC after PATCH update and aggregation

[shsakshi (SAKSHI SHARMA)]

I’m facing an issue in ISC where the entitlement data returned via APIs does not match what is shown in the UI.

Source Type: Delimited File

Use Case 1 – PATCH update not reflected in UI
I updated an entitlement using PATCH /v2025/entitlements/{id}.

• The PATCH response is successful

• GET /v2025/entitlements/{id} shows updated values (name, description, owner)

• However, the ISC UI still shows old values

Use Case 2 – Removed entitlement still visible in UI

• Removed an entitlement from the source and ran aggregation

• The entitlement is no longer returned via API (including UI entitlement API)

• But it is still visible in:

  • Entitlements Catalog

    • When trying to open it, an error is shown:
      “The server did not find a current representation for the target resource.”

  • Source → Entitlement Management → Entitlements

What I checked:

• PATCH API is working fine

• GET API reflecting the latest data

• Aggregation completed successfully

• UI refreshed/reopened multiple times

• UI entitlement API also does not return the removed entitlement

Observation:
Looks like API data is correct, but UI might be showing stale/cached or indexed data.

---

Question:

Has anyone faced similar behavior?
Is this expected due to the indexing delay in ISC, or is there any additional step required to sync the UI with API changes?

[Tursun (Shawn Tursun)]

Hi @shsakshi

Use Case 1: Yes, this is expected. For the PATCH update it takes right away, but UI make take up to 24 hours to reflect non identity impacting entitlement changes doue to SYNCHRONIZE_IDENTITIES job.

Use Case 2: Most likely is UI Serach sync delay indexing/display lag.

Thanks

[ROHPU (Pucha Rohan)]

The ISC UI doesn’t always show real‑time data. It mainly depends on indexed/search data rather than calling the entitlement API directly.
When you update an entitlement using PATCH, the change is immediately visible through the API, but the UI only reflects it after the background indexing runs.
This indexing can take some time — anywhere from a few minutes to several hours.
There’s also no manual option in the UI to refresh or force a reindex for entitlements.