Stop unchanged CRM fields from generating work
Full-record writes and feedback loops consume API capacity without improving data. Measure meaningful changes and preserve a separate reconciliation path.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
50 articles in Business integration
Page 3 of 3
Size webhook processing for bursts and redelivery
Average event rate hides the load after an outage. Keep receipt available while workers catch up within the limits of downstream services.
Read articleReduce calls per business operation before buying more capacity
A higher provider quota may help, but repeated polling and unnecessary reads can consume it quickly. Measure the request pattern behind completed work.
Read articleChoose replay speed from downstream capacity
Moving messages quickly can overwhelm the consumer or provider that originally failed. Estimate net recovery progress and reserve capacity for current work.
Read articleReview the match before accepting a Xero reconciliation
A similar amount or document number can identify a candidate, but not always the correct resource. Establish the evidence required to confirm the relationship.
Read articleReview a cleared CRM field separately from a missing one
A partial response and an intentional removal can look similar after mapping. Preserve the distinction before constructing the destination update.
Read articleReview the code between persistence and acknowledgement
The receiver's success response creates a delivery promise. Check that no process crash can leave acknowledged work without a durable recovery path.
Read articleReview the retry budget across every layer
A bounded loop is not enough when several layers retry independently. Count the maximum downstream attempts and keep one policy responsible for the operation.
Read articleCheck whether redrive changes the identity used for deduplication
Transport tools may assign new metadata during recovery. Verify that the application still recognises the original business operation.
Read articleGive support a safe path for unresolved Xero operations
Operators need to establish what happened without resending financial documents blindly. Hand over the ledger, connection scope and business escalation route.
Read articleGive the business team a readable field-ownership map
A sync policy should be understandable without reading integration code. Show who owns each value, where it travels and how disagreements are resolved.
Read articleMake replay a controlled operation
Support needs to know what an event already did before trying it again. Hand over receipt history, effect state and the provider's redelivery behaviour together.
Read articleShow support why an integration job is waiting
Delayed work needs an understandable reason and next action. Expose the relevant budget state without asking operators to inspect credentials or retry blindly.
Read articleGive every failed-message category a resolution owner
Some failures need code changes, others need a business decision. Route them deliberately so the queue does not become an unowned archive.
Read article