Solution skill
Unit.co: error handling - UnitError fields and retry policy
Complete solution
Unit.co: error handling - UnitError fields and retry policy. every failed call rejects with a UnitError carrying the HTTP status, Unit's request ID, the JSON:API error objects, and a retryable flag; log error.requestId with your support tickets. Use when hitting this exact issue with Unit.co. Not for unrelated errors or different features.
TL;DR
Every failed call rejects with a UnitError carrying the HTTP status, Unit's request ID, the JSON:API error objects, and a retryable flag; log error.requestId with your support tickets. The client auto-retries 429 and 5xx with exponential backoff and jitter honoring Retry-After, configurable via retryPolicy.
The error
error handling - UnitError fields and retry policyFix
Every failed call rejects with a UnitError carrying the HTTP status, Unit's request ID, the JSON:API error objects, and a retryable flag; log error.requestId with your support tickets. Expected: You get the expected result; the problem is gone.
Re-run the original operation and confirm the error is gone. Expected: no error, normal output.
When to use
- You hit this exact error with Unit.co.
- The symptom matches: error handling - UnitError fields and retry policy.
When NOT to use
- A different error message from Unit.co; the cause here is specific to this error.
- Unrelated Unit.co issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported against Unit.co. Source: https://github.com/fintech-sdk/unit-sdk.
Variant phrasings
error handling - UnitError fields and retry policy
Why it happens
Calls to the Unit API fail and you need the right fields for logging and retry decisions.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Source
https://github.com/fintech-sdk/unit-sdk
Evidence
Source: Calls to the Unit API fail and you need the right fields for logging and retry decisions.
Verified resolution: [fintech-sdk/unit-sdk]: every failed call rejects with a UnitError carrying the HTTP status, Unit's request ID, the JSON:API error objects, and a retryable flag; log error.requestId with your support tickets. The client auto-retries 429 and 5xx with exponential backoff and jitter honoring Retry-After, configurable via retryPolicy. POST/PATCH get an auto-generated Idempotency-Key so retries never double-submit payments; supply your own key for operations you control explicitly.
Source URL: https://github.com/fintech-sdk/unit-sdk
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_IetcKpDkETpuFu-exEUv5A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Unit.co: error handling - UnitError fields and retry policy <span>— Vectle</span></a>