A Xero timeout needs reconciliation before another invoice
A lost response leaves the outcome uncertain. Keep an operation record and a reliable mapping to the Xero organisation and resource before retrying creation.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 3 of 29
Two-way CRM sync needs field-level ownership
Two systems can share a customer record without both owning every value. Decide which source controls each field and how legitimate conflicts are resolved.
Read articleAcknowledge a webhook after you can recover it
Keep the receiver short, but do not return success before accepted work is durable. Separate delivery receipt from the business effect that follows.
Read articleRate limits belong in the integration scheduler
A retry delay inside one request does not coordinate a fleet of workers. Model the provider's shared limits and decide which work receives the available capacity.
Read articleA dead-letter queue needs a recovery decision
Moving failed messages aside protects the main queue, but it does not resolve their business outcome. Classify the failure before choosing replay, repair or deliberate closure.
Read articleNine each morning is not a fixed UTC interval
A local business schedule needs a named time zone and explicit daylight-saving behaviour. Store the user's intent before calculating individual execution times.
Read articleA field report can be saved without reaching the office
Design offline work around a durable draft, an identifiable submission and a server receipt. Each answers a different question for the person holding the phone.
Read articleA correct map pin can still be the wrong delivery address
Separate physical location, postal destination and service instructions. One address field cannot reliably carry all three meanings.
Read articleTwo decimal places do not define a money model
Separate currency, calculation precision and the point where an amount becomes payable. Display formatting cannot repair an ambiguous rounding policy.
Read articleA form is accessible only if people can finish it
Labels are the beginning. A complete form design also explains errors, preserves entered work and makes the final outcome discoverable.
Read articleA phone needs the right table task, not smaller columns
Choose a mobile presentation from what people compare and act on. Keep the same records and state while adapting the way their information is exposed.
Read articleSigning in again should not mean writing the report again
Separate the lifetime of authentication from the recovery of user work. Resume only after confirming the account, current permissions and any earlier submission outcome.
Read articleA search result is useful only in the context of a question
Build relevance tests around user intent and judged results. A high engine score does not establish that the first page answers the task.
Read articleA dependency update changes more than a version number
Review the resolved code, its build-time access and the path to production. A clean vulnerability scan is useful evidence, not a complete trust decision.
Read articleA report worker does not need the application's master key
Give each workload the authority required for its job and no unrelated administration path. Separate who may assume the identity from what that identity may do.
Read articleThe next responder needs the current state, not the whole chat
An incident handover should explain impact, active changes and the next decision. Preserve the timeline as evidence, but do not make a tired responder reconstruct it from hundreds of messages.
Read articleDeleting the customer row does not delete every copy
Retention needs a map of data destinations, an approved policy and evidence from each removal path. Backups and derived indexes require explicit treatment.
Read articleCarry document permissions into the search index
Indexing protected documents is a data-modelling job as well as a search job. Build the ingestion path so content and access rules stay attached to each other.
Read article