Skip to content

Handling retries when completion is ambiguous #72

@azender1

Description

@azender1

I’ve been testing a failure mode where:

action executes
response is lost / times out
system retries

In cases where the action likely succeeded but can’t be confirmed, retries can duplicate irreversible effects (payments, trades, etc).

How does Aura Guard handle this scenario?

Specifically:

  • do you attempt reconciliation before retry?
  • or treat retries as safe by default?

In testing, retry-by-default seems to replay side effects rather than resolve them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions