Retries and timeouts

nace uses the Python SDK's default retry policy. It retries a 408, a 429, a 5xx (unless the error says "retryable": false), a dropped connection or a timeout up to 2 times. It waits as Retry-After says, else backs off from 0.5 s up to 5 s. A retry starts only if its wait ends within 30 s of the first attempt; once started, it may run its full --timeout. So a request that fails after 30 s, such as one that hit a 120 s --timeout or a slow 529, is not retried. The CLI has no flag to change this; to retry longer, call the Python SDK with your own RetryPolicy (for example timeout=None).

nace schema-create and nace schema-version-add are never retried, because a retry could save a second schema or version. Document creates are retried safely: see Flags every tool shares.