imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

Do not resend the whole export just because the outcome is unclear.

When returning offline events, you need to know what was sent, accepted and later processed. Investigate using a versioned export and the platform's diagnostics. A generally successful HTTP response does not establish the outcome of every record.

Different responses need different next steps
  1. Rejected

    Correct the established cause before another request.

  2. Accepted, unfinished

    Follow processing using the recipient's reference.

  3. Uncertain transmission

    Investigate what arrived before deciding to retry.

A retry needs a reason and a traceable selection of records.

Can the whole export be resent after a timeout?

Not without investigating whether the first request was processed. Check available status and the destination's duplicate rules first.

Freeze the trial before retrying

Keep the export version, time, destination and a permitted internal reference for every test record. Record the business event time separately from transfer time. Do not change the event's facts simply to obtain an accepted import.

Fictional example: three reviewed enquiries need transfer. One lacks a required value and another was sent before. The team must distinguish these from the new valid record. Use harmless test information and keep personal data and secrets out of shared troubleshooting logs.

Separate initial checks from later processing

The current Data Manager flow includes initial validation and asynchronous processing. An accepted request provides a reference for further checks but does not mean that every record has finished processing. Follow the documentation for the selected method and version.

A run with validateOnly can find some errors without sending events for actual processing. It does not establish later diagnostics or attribution. Do not confuse this model with an older API's different handling of partial failures.

Observed stateRelevant checkAvoid
Request rejectedRead error type, field and destinationRepeating unchanged invalid input
Accepted, processing pendingKeep the reference and follow documented statusMarking every record complete
Diagnostics show errors or warningsReconcile scope and source recordsTreating warning and rejection as equivalent
No response or timeoutInvestigate what reached the recipientImmediately resending the whole export

Make a retry an explicit decision

Classify whether the cause needs corrected input, changed access or a later attempt. A missing required value and temporary unavailability need different responses. Follow the destination's identification and duplicate rules; platforms do not necessarily behave alike.

After an uncertain network response, inspect available status before resending. Keep the same traceable business event when the same case is intended. Document corrections and use the platform's supported adjustment or withdrawal route where applicable.

Reconcile records rather than just totals

Compare the cases selected in the business system with the export and recipient diagnostics. Separate rejected, pending, processed and unconfirmed records. Matching totals in two reports do not establish the same cases or reporting period.

The test record should include cause, correction, owner and retest. Include a genuinely new valid record so overly restrictive duplicate protection does not block new events. Bring the record to ImbaHub if you need integration help, rather than an unprotected customer export.

Sources and further reading

Questions, answered

Should every import failure retry automatically?

No. Invalid input and missing permissions normally need correction. Retries should follow the error type and documented platform conditions.

Does validation mode prove a working production import?

No. It tests some initial requirements. Later processing, actual account configuration and reporting need separate checks.

IMBAHUB

What would you like to make possible?

Keep a versioned test export and decide how to investigate each uncertain state.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.