Common Errors in the App

Learn more about the topic in this course.

Steps

1. Locate the error

   • Dashboard shows items that require attention (for example, Review required, Failed to send).

     

   • Events → Exceptions lists all active exceptions across entities.

     

   • Open the exception and select Explain to ask Pippen for a human-readable summary and next steps.

     

2. Apply the fix

   • Follow Pippen’s instructions. Most fixes fall into one of three categories:

     • Correct order or customer data (for example, invalid addresses or phone numbers).

     • Adjust connector settings or field mappings.

     • Resolve issues in a downstream system (for example, ERP, sales channel, or WMS), then retry from the app.

3. Retry the action

   • After you fix the issue, return to the entity and select Push (sometimes labeled Sync or Push) to send the update again.

4. Close the loop

   • If the exception is no longer relevant, select Dismiss to remove it from the dashboard.

   • If the item still fails, keep the exception open and contact Support with details (see Need Help?).

Common Error Patterns

Orders

• Order could not be routed

  • Likely causes: out-of-stock inventory, routing rule exclusions, or missing warehouse eligibility.

  • What to do: open Order Routing history from the order, review the run that failed, correct inventory or rules, then Push the order.

• Order failed to send to channel or ERP

  • Likely causes: connector setting or mapping changes; required attributes missing.

  • What to do: check the connector’s settings/mappings referenced in the exception; update the order data as needed; Push again.

Shipments

• Shipment could not be sent to the warehouse

  • Likely causes: invalid or missing field (for example, carrier, service, address), or mapping changes.

  • What to do: correct the field called out by the exception/Pippen; verify the warehouse connector; Push the shipping request.

Fulfillments

• Mismatch between shipping request and fulfillment (over/under-fulfillment)

  • Likely causes: quantities fulfilled differ from the shipping request.

  • What to do: confirm the WMS quantities match the shipping request; adjust quantities or split into partial fulfillments; Push the fulfillment.

• Fulfillment creation failure (ERP)

  • Likely causes: validation errors in the ERP (for example, missing line items or insufficient committed inventory).

  • What to do: correct data in the ERP; return to the app and Push the fulfillment to re-create it.

Products and catalog

• Product sync conflicts (duplicate SKUs across sources)

  • Symptom: attempts to create products from a second source fail silently as exceptions; failures appear in Events.

  • What to do: review Events for product create/update failures, reconcile SKU ownership and mappings, then Push products from the intended source.

Troubleshooting

• The exception text is not human-readable

  • Select Explain to have Pippen translate API or ERP errors into clear steps.

• Pippen suggests a data change but the retry still fails

  • Ensure you updated all relevant fields (for example, both billing and shipping phone numbers). Then Push again.

• I do not see product/inventory exceptions

  • Some catalog or inventory errors appear only in Events. Search by Entity ID from the product page.

• My search in Events times out

  • Filter by Entity ID instead of broad keywords to limit results.

Need Help?

If you need additional assistance:

• Use Ask Pippen, our AI agent, located at the top of the platform page.

• Submit a support request with as much relevant detail as possible. Learn how to submit a request.

• For urgent issues, email us directly at support@pipe17.com.

We're here to help you succeed with your operations.