Troubleshooting

Messages not being received

If you are not seeing webhooks at your destination then check the following:

• Ensure you have a pipeline that listens for that topic and that it is enabled. Shop Vector registers the Shopify webhook for a topic automatically once an enabled pipeline uses it — there's nothing to set up in Shopify's notification admin. See Pipeline Route Configuration
• Give it a moment after enabling the pipeline — webhook registration happens automatically, shortly after you save.

Delivery failure reasons

When a pipeline can't deliver an event to your endpoint, the failure appears as a badge under Recent Pipeline Failures (24H) on your dashboard. The badge shows either the HTTP status code your endpoint returned, or — when no response came back at all — a category describing the connection problem.

Your endpoint responded with an error

These are HTTP status codes returned by your downstream system.

Badge	Meaning	What to do
400, 422	Your endpoint rejected the payload as malformed or invalid.	Check your field mapping — the shape of the data being sent may not match what your endpoint expects.
401, 403	Authentication or authorization was rejected.	Verify the credentials on the pipeline destination — API key/header, OAuth2 client settings, or mTLS certificate.
404, 405	The URL or HTTP method wasn't found/allowed at your endpoint.	Confirm the destination URL is correct and that the endpoint accepts POST.
413, 415	The payload was too large, or its content type was rejected.	Reduce the payload via mapping, or confirm your endpoint accepts application/json.
429	Your endpoint is rate-limiting Shop Vector.	Shop Vector automatically backs off and retries. If it persists, enable a rate limit on the pipeline destination so requests are paced within your endpoint's limits.
500, 502, 503, 504	Your endpoint returned a server error or was temporarily unavailable.	Usually transient — Shop Vector backs off and retries automatically. If it persists, check your endpoint's health.

Retry behaviour: 429 and 5xx responses are treated as temporary and retried automatically with backoff. Other 4xx responses mean the request itself was rejected, so retrying wouldn't help — the event is recorded as failed rather than retried.

No response was received

When your endpoint can't be reached at all, there's no status code, so the failure is shown as one of these categories. Shop Vector keeps retrying these while the problem persists.

Badge	Meaning	What to do
dns_error	The destination hostname couldn't be resolved.	Check the destination URL for a typo, and confirm the domain's DNS is published and public.
connection_refused	The host was reached but refused the connection.	Confirm the service is running and listening on the URL's port, and that any firewall allows Shop Vector.
tls_error	The TLS/SSL handshake failed.	Check the certificate is valid and not expired. For mTLS destinations, verify the client certificate and CA on the pipeline are correct.
timeout	The endpoint accepted the connection but didn't respond in time.	Check your endpoint isn't overloaded or slow to respond.
network_error	A network problem prevented delivery that doesn't fit the above.	Check general connectivity to your endpoint.

About the success rate: The Delivery Success Rate (24H) figure is capped at 99.99% whenever there is at least one failure, so a small number of failures is never rounded up to a misleading 100%.