Measure useful completions under the provider limit
Request throughput can rise while the integration makes less progress. Track completed business operations, retry amplification and backlog age together.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
50 articles in Business integration
Page 2 of 3
Count resolved operations, not messages removed from the queue
A falling dead-letter count can mean replay, deletion or expiry. Measure the business outcome and unresolved age separately from transport movement.
Read articleAn invoice export timed out. Establish its outcome first
Before retrying creation, inspect the operation record and the correct Xero organisation. A timeout leaves uncertainty that another request can make worse.
Read articleA CRM value keeps changing back
Repeated reversals usually point to competing writers or a stale full-record update. Trace the field's provenance before making another manual correction.
Read articleThe provider says delivered but the application did nothing
Trace the event from acknowledgement to durable receipt and worker outcome. The missing stage determines whether to replay, repair or reconcile.
Read articleRepeated rate-limit responses need less traffic, not more workers
Identify the shared budget and stop retry amplification before increasing capacity. More concurrency can make a provider throttle harder to recover from.
Read articleStart with one representative failed message
Diagnose a small sample before moving a whole dead-letter queue. Confirm the cause, current business state and effect history before choosing a recovery action.
Read articleReconcile existing Xero mappings before enabling the new sync
A replacement integration needs to recognise documents created by the old one. Start with identity and ownership so the first run does not recreate history.
Read articleMove one CRM field's authority at a time
Transferring ownership changes which edits win. Reconcile existing values and coordinate writers before enabling the new direction.
Read articleKeep one processing owner while moving a webhook endpoint
Providers may deliver to old and new destinations during a transition. Preserve event identity and effect ownership so overlap does not duplicate work.
Read articleReplace per-process limits without doubling the allowed rate
Moving to shared coordination changes how workers obtain capacity. Roll out the new scheduler so old and new paths do not each assume they own the full budget.
Read articleDeploy the compatible consumer before replaying old messages
Failed work may use an earlier contract or expose the exact defect being fixed. Verify the new consumer against that history before releasing the backlog.
Read articleKeep each Xero request tied to the intended organisation
Concurrent jobs must not share mutable tenant context. Resolve and pass the connection explicitly so one organisation's work cannot be sent under another's identity.
Read articleSync only the CRM fields the receiving service needs
A contact record can contain more information than an operational workflow requires. Limit both transport and destination access to the purpose of the integration.
Read articleVerify the signature before trusting the webhook payload
A public endpoint must establish who sent the request and which account it concerns. Valid JSON and a familiar event name provide neither assurance.
Read articleResolve rate-limit scope from trusted identity
A client-supplied account label must not choose an unrestricted budget or another tenant's queue. Keep scheduling scope tied to the authorised integration connection.
Read articleDead-letter access can expose failed customer payloads
Failed messages often retain the original request and diagnostic detail. Restrict inspection and replay according to the data and effects involved.
Read articleReconciliation needs capacity beside live Xero traffic
Historical checks and retries share integration resources with current work. Schedule them so recovery does not starve new business operations.
Read article