{"section":"known-issues","requestedLocale":"en","requestedSlug":"expiration-date-of-special-condition-is-not-deleted","locale":"en","slug":"expiration-date-of-special-condition-is-not-deleted","path":"docs/en/known-issues/Payments/expiration-date-of-special-condition-is-not-deleted.md","branch":"main","content":"## Summary\n\n\nWhen the client configures a Special Condition for a period of time and wants to delete this configuration, only the period is deleted, the recurrence of this configuration is not deleted. This means that even if the Payment Condition scheduling configuration is removed, the `dateIntervals` field still continues to index and stops indexing the Payment Rule.\n\n\n\n## Simulation\n\n\n\n1. Set up a new Payment Condition and add the Expiration date and Recurrence from Special Condition.\n2. Use the Get Rules by Id endpoint to see the fields `beginDate`, `endDate` and `dateIntervals`. They both are filled.\n3. Then, delete the Expiration date and Recurrence from Special Condition configuration.\n4. Use the Get Rules by Id endpoint to see the fields `beginDate`, `endDate` and `dateIntervals`. The field `dateIntervals` will still be filled with the information previously deleted.\n\n\n\n## Workaround\n\n\nA possible workaround would be duplicate the Payment Condition, so the new rule will not have the `dateIntervals` setup. So the first Payment Condition can be deleted."}