A retry is a design choice.

Give repetition a meaning

When a request times out, I would avoid assuming that nothing happened. The receiving system might have completed the action before the response was lost. That possibility matters when the action sends a message, creates a record, or changes another person’s work.

I want each attempt to carry a stable identity and leave evidence of its outcome where possible. The recovery path should check that evidence before repeating the action. A retry then becomes a deliberate way to finish incomplete work, with clear handling for the cases where the outcome remains uncertain.