gRPC 0 OK vs 10 ABORTED
Both gRPC 0 (OK) and 10 (ABORTED) belong to the gRPC Status Codes category. 0 indicates that the operation completed successfully. Not an error; returned on success. Meanwhile, 10 means that the operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
Descrição
The operation completed successfully. Not an error; returned on success.
Quando você o vê
The RPC completed without any issues. This is the expected response for every successful gRPC call.
Como corrigir
No fix needed — this indicates everything worked correctly.
Descrição
The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
Quando você o vê
A transaction or optimistic concurrency check failed — for example, a read-modify-write cycle detected a conflict with another concurrent operation.
Como corrigir
Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags.
Diferenças principais
gRPC 0: The operation completed successfully. Not an error; returned on success.
gRPC 10: The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
You encounter 0 when the RPC completed without any issues. This is the expected response for every successful gRPC call.
You encounter 10 when a transaction or optimistic concurrency check failed — for example, a read-modify-write cycle detected a conflict with another concurrent operation.
Quando usar qual
For 0 (OK): No fix needed — this indicates everything worked correctly. For 10 (ABORTED): Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags.