Skip to main content

26Q3 Adhoc Requests — Status 2026-07-21

Summary​

The customer-impacting Launchpad/CRS role-name compatibility issue is now recorded as bucket story A21, owning Story BIF-9001, with implementation Task BIF-8906. The task is P2, assigned in Sprint 21464, and remains To Do; no implementation or completion is claimed.

Incident and customer impact​

An upstream CRS access-management validation change requires role names to match {APPLICATION_NAME}_{DEFAULT|CUSTOM}_{CUSTOM_NAME} and to stay consistent with client_id/company_sso_id. Launchpad's raw company-role names were consequently rejected on CRS-bound writes. The supplied incident thread also reports that Qontak One clients created after 2026-07-17 could fail login and consultant mode while the change was being rolled out.

Response and current risk​

A rollback was requested and a same-day data backfill plus retest was targeted. The available thread ends before a final confirmation, so the bucket remains at-risk until affected client IDs are enumerated, the backfill is verified, and login/consultant-mode smoke checks pass.

The planned Launchpad mitigation formats only CRS-bound company-role create/edit payloads as Qontak_Custom_<raw_name> (after the upstream application-name and identifier contract is confirmed). Raw values remain unchanged in Launchpad storage, local/API responses, audit records, and Loyalty integrations. A feature toggle controls rollout and preserves a safe rollback path.

Follow-ups​

  • Confirm the authoritative application name, casing, and client_id/company_sso_id source with the upstream CRS owner.
  • Enumerate affected post-2026-07-17 client IDs and role records; record backfill counts and verification evidence.
  • Exercise staging and production smoke checks for login, consultant mode, and custom-role create/edit before enabling the formatter by default.
  • Keep the PRD acceptance criteria and the BIF-9001/BIF-8906 Jira relationship aligned as the task moves out of To Do.