Getting a Pass When You Expect a Fail
This usually means activity context wasn't sent with the code. A code approved for one activity can look valid if you only check the code itself. Always send country and activity together.
Confusing Invalid, Delisted and Mismatched
These are three different problems and need three different responses. A properly built TRACES API integration for ERPs returns distinct error semantics for each, so check that your integration surfaces the specific reason, not a generic failure flag.
Authentication Failures Mid-Run
Token-based authentication with rotation means a long-running bulk job can outlive its token. Build in a refresh step for bulk requests rather than assuming one token covers the whole batch.
Bulk Requests Timing Out
Large catalogue validations should be chunked rather than sent as one enormous request. Check documentation for recommended batch sizes before running your first full catalogue sweep.
Results Not Appearing in the Audit Trail
If a validation ran but didn't log, check that the request completed rather than erroring silently.
Watch a demo and walk through error responses with the team that built the API.
Top comments (0)