Handle pending CEPs, not-found results and rate limits

Distinguish missing evidence from a negative claim

A payment can be reported while its CEP is not yet available. Incorrect dates, amounts, account identifiers or institution mappings can also prevent retrieval. A not-found outcome describes the submitted lookup; it does not prove that no payment ever occurred. Ask for the exact operation details before guessing nearby values.

Wait for the actual upstream condition

GridZen returns a durable task and processes the integrated cepmex SDK sequence under a shared HTTP budget. A 202 response means accepted, not verified. Rate limits and service errors produce bounded delays. An access challenge stops the affected route for review. Increasing client concurrency cannot remove that restriction.

Do not solve challenges by rotating IPs, creating replacement sessions or falling back to a browser. Keep originals already acquired so recovery does not start from zero.

Recover using the original request

After a submission timeout, query the original idempotency UUID. If the task exists, continue reading it. A service status check should not create a new supplier query. Show queue state and reason to operators; give the customer a specific next step rather than a silent failure. Do not promise a fixed completion time while the source is restricted.