Redis Cache Handling during Patch Upgrades
During application upgrades, Redis cache must NOT be fully deleted. Redis stores reusable data to avoid repetitive database queries and enhances performance. Instead of quering the main DB, it directly fetches from the Redis Cache DB. Clearing the entire Redis cache forces the system to rebuild all data, causing performance degradation for several days.
Patch 24 - Specific Key Removal Summary
Change: Service portal label/tooltip updates
Action: Remove key pattern: getstaticformlabellistquery_8ad3797e-01e4-41f7-ae4b-1ed587f0b4d7
Only remove above key pattern mentioned from the Redis Cache DB. DO NOT remove entire Redis Cache.
Upgrade Scenarios
While upgrading from patches with multiple in-between patches, refer the below upgrade use-case scnearios. Below are hypothetical examples for understanding purpose and not actuals.
Scenario 1: Upgrading from Patch 20 → Patch 27
Patch changes:
No Redis key changes: 20, 21, 22, 23, 25, 27
Keys to remove:
Patch 24 → 1 key
Patch 26 → 1 key
Action:
Before or during upgrade to 27, remove the Redis key patterns listed in Patch 24 and Patch 26 release notes only.
Scenario 2: Upgrading from Patch 26 → Patch 27
Patch changes:
Patch 26 → 1 key removal
Patch 27 → No changes
Action:
No changes needed, since while you were on Patch 26, the key was already previously removed. Hence, for upgrading from Patch 26 to Patch 27, no changes are needed.