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 inquiries 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 state | Relevant check | Avoid |
|---|---|---|
| Request rejected | Read error type, field and destination | Repeating unchanged invalid input |
| Accepted, processing pending | Keep the reference and follow documented status | Marking every record complete |
| Diagnostics show errors or warnings | Reconcile scope and source records | Treating warning and rejection as equivalent |
| No response or timeout | Investigate what reached the recipient | Immediately 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.