Troubleshooting

When a run fails, the run details page is the best place to start. It shows the error message, the step that failed, and any relevant logs.

Source unavailable

If a pipeline cannot reach the source:

• Check that the credential is correct and has not expired.
• Verify the host, path, or endpoint is reachable from VendorGate.
• Confirm the source system allows VendorGate's IP addresses if there is an allowlist.

Contract failures

If a file fails validation:

• Review the validation report to see which rules failed and on which rows.
• Test the contract against the failing file to reproduce the issue.
• Adjust the rules if the vendor changed their format.

Delivery failures

If the file validates but delivery fails:

• Check the destination credential.
• Verify the destination path, bucket, or endpoint exists.
• Confirm the destination has enough space or quota.

Slow standardizers

If a standardizer takes longer than expected:

• Reduce the size of lookup datasets if possible.
• Simplify complex expressions.
• Split one large standardizer into multiple focused standardizers.

API monitor false alarms

If a monitor flaps between down and up:

• Increase the number of consecutive failures required before alerting.
• Increase the timeout if the endpoint is occasionally slow.
• Add retries to tolerate transient network issues.

Getting help

If you cannot resolve an issue, capture the run ID and error message and contact your account administrator or VendorGate support.