Decide what may degrade
Analytics, recommendation feeds or non-essential notifications can often fail asynchronously. Payment verification, stock reservation and security checks should fail explicitly when correctness cannot be guaranteed.
Give every incident a reference
Log structured context and a stable reference without leaking credentials. Track latency, database time, queue age and provider error classes before guessing at root causes.
Retry behind safe boundaries
Use queues, idempotency keys and reconciliation jobs where recovery is expected. Keep operator tools for replay or repair auditable.
Project-specific contracts win.
These pages describe Thonem implementation patterns. Exact endpoints, payloads, credentials, retry rules and provider capabilities must be taken from the deployed project and its provider documentation.