Add Monitored Events to a Policy

A Monitored Event tells an Alert Policy which failures to watch for. A policy can have multiple monitored events, each covering a different category of failure or a different set of connections. When any of them fire, the policy creates an Alert.

Open the Monitored Events panel

1. Go to Account settings → Alert Settings → Alert Policies and open the policy you want to add events to.
2. Scroll to the Monitored Events card at the bottom of the page.

Each row shows the event’s status toggle, name, and description. Use the toggle to enable or disable an event without deleting it. Use the icons at the end of the row to edit or delete it.

Add an event

1. Click + Add Event.

1. Enter a descriptive Event Name — this is what appears in the policy’s Monitored Events list, so pick something that describes the intent (for example, Critical Order Failures or ShipStation Inventory Errors).
2. (Optional) In Connections, select one or more connections to restrict the event to. If you leave this empty, the event fires for any connection on your account. Use this to scope a policy to a specific store, warehouse, or marketplace integration.
3. Under Select Events, expand one or more categories and check the specific events this monitor should cover.

1. Click Add Event.

Available event categories

Each category can be expanded with the arrow next to its name, and each category has a master toggle that enables all of its events at once.

Orders

Failures in the sales order pipeline.

• Import Failed — an order could not be pulled in from a store.
• Export Failed — an order could not be sent to its destination warehouse or fulfillment provider.
• Order Creation Failed — the order record itself could not be created in DropStream (for example, due to bad data).
• All Order Related Failures — enables every event in this category, including variants that may be added over time.

Returns

Failures in the sales order return pipeline.

• Import Returns Failed — a return could not be pulled in from the source store.
• Sales Order Return Creation Failed — the return record itself could not be created in DropStream.
• All Sales Order Return Failures — enables every event in this category.

Purchase Orders

Failures in the purchase order pipeline.

• Import Purchase Orders Failed — a purchase order could not be pulled in.
• Purchase Order Creation Failed — the purchase order record itself could not be created.
• All Purchase Order Failures — enables every event in this category.

Shipment

Failures while DropStream is processing shipments.

• Store Error — a shipment update could not be pushed back to the originating store.
• Warehouse Error — a shipment could not be processed at the fulfilling warehouse.
• Shipment Process Error — a shipment failed during DropStream’s processing pipeline.
• Shipment Error — a shipment could not be recorded against its order.
• Shipment creation Error — the shipment record itself could not be created.

Inventory

Failures in the inventory sync pipeline.

• Inventory Import Error — inventory counts could not be read from a warehouse.
• Inventory Export Error — inventory counts could not be pushed to a store.
• Store Inventory Error — the store rejected a specific inventory update.

Scoping tips

• If you want all failures for a category to alert with the same policy, check the category’s All … event rather than each individual one — new event types added later will automatically be covered.
• To get different grouping behavior for different entities (for example, per-store alerts for one warehouse and per-policy alerts for another), create separate policies, each with its own monitored events scoped to the relevant connections.