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 / Global
Cobnex blog
AI implementation, software architecture and cloud operations for teams worldwide.
50 articles in Business integration
Page 1 of 3
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 articleSave the integration intent before sending it to Xero
A durable operation record gives retries and support a shared source of truth. Record the target organisation and expected request before making the external call.
Read articleEncode the field policy beside the mapping
Keep direction, authority and empty-value behaviour in one reviewed definition. Scattered conditionals make the same field behave differently across imports and live updates.
Read articlePut a durable inbox behind the webhook endpoint
Store verified event identity and processing state before returning success. Let workers handle slow business logic without losing the ability to retry.
Read articlePersist the next eligible attempt instead of sleeping in a worker
A durable retry time lets the scheduler pause one provider scope while other work continues. Preserve the original operation identity across attempts.
Read articlePreserve business identity when a message is redriven
Queue metadata can change during recovery. Put the durable operation identity in the application message and use it at the effect boundary.
Read articleLose the Xero response after the test invoice is created
Reproduce an unknown outcome in a safe organisation. The integration should recover the original result rather than create another invoice automatically.
Read articleEdit the same contact in both systems before sync runs
A controlled conflict shows whether ownership rules survive real timing. Verify the chosen value and the evidence retained for the losing change.
Read articleDeliver the same webhook while the first worker is still running
Concurrent duplicates expose gaps that sequential retries miss. Verify receipt deduplication and the actual business effect independently.
Read articleThrottle one account while another keeps working
A scoped failure test shows whether shared workers preserve fairness. The unaffected account should continue within its own provider budget.
Read articleReplay a failed command after the record has changed
Recovery must respect current business state. Test a delayed command against a newer revision before allowing broad replay.
Read articleTrack unresolved Xero outcomes separately from retry counts
A busy retry loop can look active while business documents remain uncertain. Measure confirmed mappings, unresolved age and reconciliation results.
Read articleCount ownership conflicts before they become silent overwrites
A successful API update can still violate the sync policy. Measure protected fields, unresolved conflicts and repeated reversals alongside transport health.
Read articleMeasure webhook receipt and completion separately
A provider can see successful delivery while the application backlog grows. Track durable acceptance, processing age and final effects as different stages.
Read article