Known Issues and Behaviors

Learn more about the topic in this course.

Known Issues and Workarounds

• Some exception messages are not human-readable or lack a clear call to action

  • Workaround: Open the exception and select Explain.

  • If resolving a data submission errors, follow the steps Pippen provides, and attempt to Push the entity after adjustment to the data or settings involved.

    • Please contact support if the error returns or the change does not have the desired effect.

• Order routing terminology

  • “Out of stock,” “Not eligible,” and similar outcomes are shown in Order Routing history.
    

  • Workaround: Always open Routing history from the order details view to see the exact rule or inventory condition which blocked routing.
    

• Manual fixes require a retry from the app

  • After you correct data in a channel, ERP, or WMS, there many not always be automatic retry logic in place

  • Workaround: Return to the relevant entity in Pipe17 and select Push or Sync to resend.

• Product catalog conflicts do not always raise exceptions

  • When two sources try to own the same SKU, failures messages will be shown in Events.

  • Workaround: Use Events query with the Product’s internal id (Entity ID) to find the failed event messaged and reconcile SKU ownership.

    • Note: Pipe17 works best if the user selects a single source of product catalogue data prior to time of ingest.

• Event search performance

  • Broad keyword searches can return too much data; this may lead to timeouts.

  • Workaround: When searching in Events Log, always populate as many filters as possible at the top of the page (eg. Date, Keyword, Direction, Integration etc).

  • The most direct approach is the populate the Entity ID value from the entity’s URL or use See events from the Entity Details page to pre-filter your query.

• Exception categories and filters

  • When searching Exceptions, you will see a complete list of every warning/failure raised by our platform logic.

    • The Exception Categories filter may not be available when using individual entity table pages (Orders, Shipments, Products etc)

  • Workaround: Use Exceptions search, and filter by entity first (order, fulfillment, shipping request), then move to refine using other filters/date as needed.

• Returns and inventory

  • Return flows and inventory exceptions have limited exception coverage in some areas.

  • Workaround: Rely on Events and the entity page for status, then use Push where available.

    • For Inventory, we recommend using Keyword search + Direction + Integration to better tailor matching results.

Troubleshooting

If a known issue blocks you from completing a workflow, capture event details and include the Entity ID, integration, and the action you attempted when you contact Support.

You can also query Pippen and provide the output as part of the support request context.

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.