Ballerina connector retry policy and duplicate writes on non-idempotent operations
Ballerina HTTP client and other connector clients support a retry attribute and a configurable retry policy with back-off and max attempts. The retry mechanism reissues the same request on transient failure. For non-idempotent write operations this raises uncertainty about duplicate execution, as the runtime does not automatically add idempotency keys or coo
ballerina