Sync failure handling

This post details Trello's sync failure handling mechanisms for mobile applications. It covers categorizing network errors into temporary and permanent, implementing exponential backoff for temporary errors with retry caps, and ensuring idempotence through client-generated UUIDs to prevent duplicate actions. It also discusses a 'last-writer wins' conflict resolution strategy for most data and a method for reverting unsynced data by allowing future server GET requests to overwrite local changes.