The events section is where you can monitor activity and the flow of data into and out of Pipe17.
In this article
Search and filter events
The Events page shows a log of all activity on your account. Although it can look a little overwhelming if the volume of activity is high, you can use the search and filtering options to narrow it down to just what you need to see.
If you want to find information about a specific entity, such as an order or product, you can enter the order ID (or product name, or SKU) to see only the events relating to that entity. You can also use the Entity filter to narrow down the list just to orders, or products.
The operation filter can be helpful if you're searching only for specific types of events, such as order creation or inventory update.
You can use the direction filter to specify whether you want to see events about information flowing into Pipe17 (for example, a new order from your selling channel) or information flowing out of Pipe17 (like a shipping request being sent to your 3PL).
The integration filter can be used for narrowing down to one (or more) specific connectors.
The status filter refers to the status of the event - it can be useful to filter for "failed" events only if you're trying to troubleshoot an issue with your orders.
There are 3 possible statuses for an event:
- Completed: A completed event has been successfully sent or received by Pipe17.
- Acknowledged: An acknowledged event has been sent by Pipe17, but we have not received a success message from the receiving system. Most of the time, you can consider an acknowledged event to be successful, and it will eventually transition to Completed status. If not, and you believe the data in the event was not successfully sent, contact our support team.
- Failed: The event is failed if an error is generated by the receiving system. You can view the event details to troubleshoot the problem, and rerun the event when the underlying issue is resolved.
See event details
Clicking on "Details" next to an event will show you the actual request and response details of that event. Usually, you'll want to look at the "response" section to identify a particular success or error message.
You're trying to identify who changed your product from a simple to a bundle. To find the event where this happened, copy the SKU of your product and enter it in the Search bar of the Events page (tip: you can also use the filters for entity = Product and operation = Update to narrow it down further!)
Look at the "Integration" column to identify who/what made the change. A "System" event indicates a change made by a user via the Pipe17 portal, as opposed to an automated event by an integration.
Click on "Details" on the two System events to see the exact event data. You'll see that the request body contains some new bundle items, indicating this is the event where that change happened! Further down in the "Whole response details", you'll also see the email address of the user that made the change.
Here are some other examples of how the events page can be useful:
- Filter by "Integration = Order Routing Engine" and search for an order ID to see exactly why/how an order routed to a specific fulfillment location.
- Filter by "Integration = Your 3PL" and "Status = Failed" to see recent failed events and troubleshoot your connector.
- Filter by "Integration = Your Selling Channel", "Operation = Create", and search for an order ID to see when recent orders were pulled from your selling channel.
Rerun an event
You can click the "Rerun..." button to the right of an event to replay it. This is useful if the event was originally failed and the problem that caused the failure has now been fixed.
To rerun events in bulk, use the checkboxes to the left of the event name to select which ones you wish to rerun, then click "Rerun..." at the top of the page.
|Rerunning events can have negative consequences. Make sure you actually want to re-send the data associated with the event, otherwise you may run into data duplication issues like double shipping an order if you rerun a "shipping request creation" event.