Flexport Failure Classification

Overview

Do not convert every failure into a retry. First identify the surface and operation class, then distinguish authentication, authorization, validation, provider availability, and ambiguous mutation outcomes.

Prerequisites

• Redacted surface and operation name
• HTTP status or JSON-RPC error plus documented provider code/message
• Knowledge of whether the failed operation could mutate freight or trade records

Instructions

Step 1: Identify the surface

Label OAuth token, REST v3, MCP JSON-RPC, or webhook delivery; each has different failure semantics.

Step 2: Protect evidence