Tag: incident-response
ThreadTrak — Founder access
A Chrome extension for X/Twitter: map threads, queue replies, and keep conversations actionable.
Handling 429s and Retry-After correctly in HttpClient
A production playbook for honoring Retry-After and stopping retry amplification when a dependency throttles your .NET service.
Correlation IDs in .NET: trace one request across services and jobs
A production playbook for a single correlation ID contract in .NET so requests and jobs can be traced end-to-end across boundaries.
The real cost of retry logic: when “resilience” makes outages worse
Retry storms don’t look like a bug — they look like good engineering until production melts. Here’s how to bound retries with stop rules and proof.
Thread pool starvation: the silent killer of ASP.NET performance
When CPU looks fine but everything times out: how thread pool starvation happens, how to prove it with real signals, and the smallest fixes that stop repeat incidents.
Timeouts first: why infinite waits create recurring outages in .NET
Infinite waits do not look like crashes. They look like calm dashboards and growing backlog. This is the production playbook for adding time budgets safely in .NET.
Why your background jobs hang forever (and no one notices)
Queues and scheduled jobs fail quietly: missing timeouts, missing heartbeats, and retries that hide failure. A practical runbook-style playbook for .NET systems.
Why agents loop forever (and how to stop it)
A production playbook for preventing infinite loops: bounded retries, stop conditions, error classification, and escalation that actually helps humans.
Why exchange APIs "randomly" ban bots (and how to prevent it)
A production-first playbook to avoid bans: permissions, rate limits, auth hygiene, and traffic patterns that keep trading bots alive.
Timestamp drift: the silent cause of signature errors
Why bots suddenly start failing with 401/403 or signature errors, and the production fixes that stop timestamp drift from taking you down.