From software problem to a clear next step.
Choose a topic and what you need to do next. Add a search phrase to find a specific problem.
Browse 20 topics
Explore the playbooks
1500 guides · Page 4 of 60
-
Triage a sandbox and production API mixup
Separate endpoint, credential, resource, and environment labels so an API environment mismatch can be corrected without crossing data boundaries.
-
Prioritize wrong-environment API calls
Rank sandbox and production mixups by data exposure, durable side effects, caller reach, and confidence in a safe configuration correction.
-
Investigate sandbox and production API configuration
Trace environment selection, endpoint construction, credential labels, and resource markers to explain an API mixup with safe synthetic fixtures.
-
Verify API endpoint and environment separation
Test matching and crossed API configurations, resource markers, credentials, and process restarts so sandbox and production work cannot silently mix.
-
Learn from API environment mixups
Maintain environment manifests, safe labels, crossed-configuration fixtures, and review signals so test and production API work stays visibly separate.
-
Triage an OAuth redirect URI mismatch
Compare registered and sent redirect values, callback state, session, and environment so an OAuth failure stays within the authorization boundary.
-
Prioritize OAuth callback failures safely
Rank redirect and callback failures by account blockage, state-binding risk, environment reach, and confidence in a narrow registration or session fix.
-
Investigate OAuth redirect validation failures
Trace authorization request construction, URI registration, callback state, session binding, and token exchange without retaining sensitive codes.
-
Verify OAuth redirect and state handling
Exercise exact URI matches, host changes, stale sessions, missing state, and environment variants so OAuth callbacks cannot cross their authorization boundary.
-
Learn from OAuth redirect mismatches
Maintain per-environment redirect registrations, state fixtures, session ownership, and review signals so callback changes stay exact and recoverable.
-
Triage a service account API permission gap
Compare allowed and denied operations, resource roles, scopes, tenant context, and credential labels before requesting more service-account access.
-
Prioritize service account API access gaps
Rank service-account denials by blocked durable work, tenant reach, authority expansion, and confidence in a least-privilege correction.
-
Investigate service account role and scope mismatches
Trace service identity, token claims, resource binding, endpoint policy, and local handling to explain one API permission failure.
-
Verify least-privilege API access for a service account
Exercise allowed, denied, wrong-tenant, and wrong-operation cases to prove service-account access is sufficient without silently expanding authority.
-
Learn from service account permission drift
Maintain operation-to-role matrices, denied fixtures, identity ownership, and recurrence signals so service access remains least privileged and diagnosable.
-
Triage API client connection pool exhaustion
Find whether pool wait, socket reuse, response handling, concurrency, or remote latency first consumes API client capacity.
-
Prioritize API connection pool exhaustion
Rank pool pressure by blocked essential work, shared caller reach, resource cost, and confidence in a safe capacity or release correction.
-
Investigate API connection reuse and pool leaks
Trace pool acquisition, socket reuse, response consumption, release, timeout, and retry paths to explain concurrent API client pressure.
-
Verify API client connection pool limits
Exercise concurrent, slow, failed, cancelled, and restarted requests to prove connections release correctly and bounded callers do not starve each other.
-
Learn from API connection pool saturation
Maintain transport lifecycle rules, bounded load fixtures, concurrency ownership, and recurrence signals so pool pressure remains measurable and recoverable.
-
Triage an API dependency outage fallback
Separate dependency failure, local state, stale fallback, and recovery evidence before deciding whether an API consumer can continue safely.
-
Prioritize API dependency outage impact
Rank dependency failures by durable work blocked, stale-data consequence, caller reach, and confidence in a bounded fallback or reconciliation.
-
Investigate API dependency failure boundaries
Trace local request, dependency transport, failure classification, fallback or pending state, and later reconciliation to explain an outage-shaped result.
-
Verify API fallback and recovery behavior
Test healthy, temporary failure, permanent rejection, stale fallback, recovery, and unknown-write paths so API degradation stays safe and visible.
-
Learn from API dependency outages
Maintain failure classifications, fallback freshness rules, recovery fixtures, and ownership signals so dependency outages do not become misleading data.