Duplicate writes on retried Remix actions and POST-Redirect-GET limits
A design goal is to ensure mutations handled by a Remix route action are applied once even when a client retries a request before receiving a response. Remix processes mutations in route action functions for POST, PUT, PATCH and DELETE requests and the conventional success response is a redirect to a GET route. The framework does not provide built-in idempot
remix