An SI's charter read is retried on a YugabyteDB conflict instead of answering 503

Shipped

October 11, 2026 at 10:50 PM UTC

Author

Kamo

Commit

b460762

GET **************** (I1) resolves the charter in one read-only transaction of 15-25 queries. One "Restart read required" (40001) answered 503 CHARTER_UNAVAILABLE; AIService's brief read then answered 503 and the KamoAI runtime held the SI for five minutes as a provider outage (seen on the sp00verify test SI at 22:30:40, mid-conversation). **************** is now @RetryOnDbConflict: the read runs again in a new transaction. It is a read, so it is safe to repeat.