{"section":"known-issues","requestedLocale":"en","requestedSlug":"competing-authorization-rules-generated-when-receiving-a-delaytocancel-value","locale":"en","slug":"competing-authorization-rules-generated-when-receiving-a-delaytocancel-value","path":"docs/en/known-issues/Payments/competing-authorization-rules-generated-when-receiving-a-delaytocancel-value.md","branch":"main","content":"## Summary\n\n\nWhen the connector updates the delayToCancel field after the first authorization response, VTEX gateway enqueues a new authorization flow but keeps the original one active. The visible symptom is that two retry plans run in parallel, which can cancel the VTEX order by the lowest delay time.\n\n\n#### Simulation\n\n\n\n-\n\nStart a transaction with an initial delayToCancel of 3 hours (10800s) on the authorization response.\n\n\n\n-\n\nReturns a new delayToCancel of 4 days (345600s) in a subsequent response.\n\n\n\n-\n\nObserve that both authorization “plans” continue: retries from the first plan keep occurring (e.g., every hour up to 3 attempts) while the second plan also schedules retries (e.g., every 4 hours up to 24 attempts). The order may be canceled by the first plan before the second plan’s retries complete\n\n\n\n\n\n#### Workaround\n\n\nPrefer sending the longest/most conservative delayToCancel in the first authorization response to avoid enqueuing a short plan that will cancel early."}