Retry policy

How it works

Retry transient network errors. Do not retry a 403 the same way. Exponential backoff avoids a stampede. A cap stops a weekend loop. Resume so a retry does not resend finished bytes.

A partner host refuses connections for nine minutes. The job retries at 1, 2, 4, and 8 minutes and lands on the fourth try. A job that retries a 403 quota error every second locks the account.

How it differs

A retry policy is not resume. Resume continues one transfer. Retry starts another attempt.

Immediate retry of a down host wastes the window.

Log each attempt.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For retry policy, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive retry policy files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.