tRPC Client with Retry Logic — v0.1.6
tRPC Client with Retry Logic
Introduced in: v0.1.6
Overview
myProp communicates with the AgentOS platform via letmc.com API endpoints. As of v0.1.6, the tRPC client that powers this communication is configured with a timeout, standardised JSON headers, automatic retry logic, and response interceptors — making API calls more resilient and predictable for all portal users.
Configuration
Request Timeout
All outbound requests to the AgentOS API are subject to a 30-second timeout. If a response is not received within this window, the request is aborted and the retry mechanism (see below) takes over.
This prevents long-running or stalled requests from degrading portal performance.
JSON Headers
Every request is sent with the following HTTP headers automatically applied:
Content-Type: application/json
Accept: application/json
This ensures consistent serialisation and deserialisation of data exchanged with the AgentOS API.
Retry Logic
When a request fails — due to a network error, timeout, or a retryable API error — the client will automatically retry the request according to the following policy:
| Parameter | Value |
|---|---|
| Maximum retries | 3 |
| Delay between retries | 1,000ms (1 second) |
This provides resilience against transient failures without overwhelming the API or blocking the user for an extended period.
Response Interceptors
Response interceptors are registered on the tRPC client to:
- Centralise error handling — Errors returned by the AgentOS API are caught and normalised before reaching application logic.
- Normalise responses — Ensures a consistent response shape is passed through the application regardless of minor API variations.
- Surface meaningful error states — Application components receive actionable error information rather than raw HTTP error objects.
How It Affects Portal Users
- Improved reliability — Temporary connectivity blips or brief AgentOS API interruptions are handled transparently; users are less likely to see error states caused by one-off failures.
- Faster failure detection — The 30-second timeout ensures users are not left waiting indefinitely if a backend service is unresponsive.
- Consistent data handling — Standardised headers and response normalisation reduce the likelihood of data parsing errors across portal features such as maintenance tracking, tenancy details, financial statements, and messaging.
Target API
All tRPC client requests are directed at the AgentOS (letmc.com) API, which is the authoritative data source for agency, property, tenancy, and financial information surfaced in the myProp portal.