{"section":"known-issues","requestedLocale":"en","requestedSlug":"changes-not-persisted-when-editing-expiration-date-in-payment-rules","locale":"en","slug":"changes-not-persisted-when-editing-expiration-date-in-payment-rules","path":"docs/en/known-issues/Payments/changes-not-persisted-when-editing-expiration-date-in-payment-rules.md","branch":"main","content":"## Summary\n\n\nWhen editing the Expiration date field (API property: endDate) of a payment rule in the Admin, the interface shows \"Saved successfully,\" but the Ul keeps showing the previous date; the adjustment does not persist visually or functionally.\n\n\n#### Simulation\n\n\n\nIntermittent reproduction.\n\n- Navigate to Admin > PCI Gateway > Payment rules, and open the specific rule\n- Add a special condition: Expiration Date (internal test with 31/12/2025: GMT -3)\n- Click Save and confirm the Ul shows \"Saved successfully.\"\n- Change the date to another one and save it again. (internal test with 31/12/2026: GMT -3)\n- Observe the rule details; the Expiration date doesn't show the updated value. (internal test with 31/12/2025: GMT -3)\n\n\n#### Workaround\n\n\n\nRetry saving the Expiration date: A subsequent attempt to save the Expiration date tends to reflect correctly (worked in internal tests after a failure)."}