Issue description
In some subscriptions, the START_ENTITLEMENT event returned before a CHANGE contains:
- product = null
- plan = null
- catalogEffectiveDate = null
This causes failures in PNL, which relies on the previous START_ENTITLEMENT to identify the product/plan before the CHANGE.
Observed pattern
The issue seems to happen when subscription creation (START_ENTITLEMENT / START_BILLING) and plan CHANGE occur within a short time window.
Notably:
- The START_BILLING event (same effectiveDate) contains product and plan correctly populated.
- Only START_ENTITLEMENT is missing catalog information.
Example subscription
subscriptionId: 2bb94eb2-53cc-4d9c-96cb-8d9e46e8e8a0
Relevant events (excerpt)
START_ENTITLEMENT
{
"eventType": "START_ENTITLEMENT",
"effectiveDate": "2026-04-08T20:40:40.000Z",
"catalogEffectiveDate": null,
"plan": null,
"product": null,
"serviceName": "entitlement-service",
"serviceStateName": "ENT_STARTED"
}
``
START_BILLING (same effectiveDate)
{
"eventType": "START_BILLING",
"effectiveDate": "2026-04-08T20:40:40.000Z",
"catalogEffectiveDate": "2026-04-06T12:00:01.000Z",
"plan": "PL_DTVGO_BR_AMZMAXPP_PFSN_BD_201_DISNEYPLUS-SKYFUT04",
"product": "DTVGO_BR_AMZMAXPP_PFSN_BD_201_DISNEYPLUS"
}
``
{
"eventType": "CHANGE",
"effectiveDate": "2026-04-09T14:40:27.000Z",
"plan": "PL_DTVGO_BR_AMZMAXPP_PFSN_BD_001_DISNEYPLUS-SKYCANFUT2705",
"product": "DTVGO_BR_AMZMAXPP_PFSN_BD_001_DISNEYPLUS"
}
`
Impact
- PNL fails to process plan changes.
- Customers performing quick sign‑up + plan change are impacted.
- Affects upgrade/downgrade subscription flows.
`