Restore the previous behaviour after a model regression
Confirm the affected configuration and contain new failures before changing prompts in place. A known prior release is easier to assess than an unrecorded emergency variation.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 13 of 29
Give the reviewer the contradiction, not the whole queue
A useful exception record says which fields disagree and shows their evidence. That lets reviewers resolve the problem without repeating the extraction process manually.
Read articleInvestigate a payload found in unexpected diagnostics
Establish which data was copied, who could access it and which path created it. Contain further logging while preserving the evidence needed to assess the incident.
Read articleStop an over-budget run with a recoverable status
Prevent new work, account for operations already accepted and preserve the useful result. Cancelling the conversation alone may leave costs and effects running in the background.
Read articleRoute an unresolved answer to someone who can help
A handoff should carry the unanswered question and evidence already checked. Make the next owner clear without promising work the application has not actually submitted.
Read articleTrace a production defect to the owning module
Follow the business operation and its state change before assigning the incident. Technical layers can obscure which module owns the violated rule.
Read articleReconcile the outbox with the consumer outcome
An outbox row marked published does not prove the business effect completed. Trace the event through publication, delivery and consumer state before replaying it.
Read articleResolve a command whose response was lost
Keep the original operation identity while establishing what happened. A new key can turn recovery into a second business action.
Read articleIdentify the caller behind a compatibility incident
A server can be healthy while one supported client is broken. Trace the failing contract and client behaviour before treating the incident as a general outage.
Read articleContinue a saga with one irreversible effect
When a completed step cannot be undone, stop describing recovery as rollback. Establish the remaining business options and preserve the effects already known to exist.
Read articleTrace the job that ran under the wrong account
Contain further work, preserve the job's trusted context and identify every affected artifact. A wrong-tenant job can create consequences beyond its final response.
Read articleDiagnose an event that parsed but meant the wrong thing
When records look plausible but are wrong, trace how the consumer interpreted the message. Successful deserialisation can hide a semantic change.
Read articleFind which cache is still serving the old value
Trace one response through browser, edge and application layers before clearing everything. A broad purge can hide the cause and overload the source.
Read articleA migration is waiting. Find the blocker before retrying
Repeatedly launching the same command can create more contention. Inspect the active database work and choose a controlled recovery action.
Read articleTrace a deadlock to the order of resource access
Retrying can recover one request, but repeated deadlocks need a clearer picture of which transactions acquire which resources.
Read articleKeep one cutover record everyone can follow
During a migration window, conflicting status reports create avoidable risk. Record the current phase, evidence and decision owner in one shared run log.
Read articleDiagnose a platform policy failure at its effective scope
A workload can inherit several layers of control. Identify which rule applies to the actual identity and resource before changing permissions.
Read articleThe restore completed but the application will not start
Diagnose compatibility and dependencies before repeating the restore. A successful data job can leave the application missing configuration, keys or a usable identity.
Read article