Exceptions are essentially errors in Pipe17 that we are unable to resolve based on your current configuration. These can often appear due to outages on platforms, or due to other issues as well.
The exceptions themselves will attempt to explain the situation with the text but, may not always be entirely clear in every scenario. If there is any confusion, it is highly suggested you reach out to the Pipe17 support team with any examples for further clarification.
In this Article
- When do exceptions appear?
- How do I resolve exceptions?
- Why do I see an exception when everything looks fine?
When do exceptions appear?
Exceptions can be generated for a variety of scenarios, including orders unable to be routed, fulfilled, or during downtime on any connector. Commonly, you will often receive exceptions when there is a routing configuration that cannot be completed, such as there not being a valid location.
How do I resolve exceptions?
Exceptions often occur due to a configuration issue. In most cases, if you are unsure of the exact cause the the exception itself should have a message, which will also act as a clue, or indication as to what may be happening. Some examples may include, having order routing - and there is no valid destination for your rules. If the order is able to be routed but, there is a problem during the fulfillment or shipping process - you may also receive another exception, indicating there was an issue.
Custom mapping can also create exceptions. The errors with custom mapping may not be clear in every instance, as you are modifying the information used in connection with these services - often this may appear as an HTTPs code, or a response code specific to that platform.
Why do I see an exception when everything looks fine?
Exceptions do not always automatically clear once you have resolved the configuration problem. If for example, you had no valid locations to route an order to previously - the order may not still be routed. Rerunning the order should update the status, and let it continue.
If you are seeing the exceptions even though it has been routed - it's likely not cleared yet. You can manually clear exceptions by clicking the "x" in the box, or from bulk in the order list. Exceptions can stay even once resolved if not cleared, and this will prevent you from being notified further (unless further issues persist).