The Resolution Engine is part of the Automation Engine and helps reduce manual exception handling across your organization. It automatically detects and clears eligible exceptions based on scheduled rules, keeping your operations running smoothly with less manual oversight. By applying default and public rules, the system ensures that exceptions are addressed promptly and consistently.
Key Advantages
The Resolution Engine reduces the burden of manual exception handling by:
Automatically clearing issues that no longer require action coming from exceptions.
Preventing unnecessary notifications for exceptions already resolved.
Allowing teams to focus only on exceptions that genuinely require review or intervention.
This automation ensures cleaner workflows, fewer distractions, and faster operational response times. For more details, see the Order Exceptions Engine article.
How It Works
The Resolution Engine runs on two distinct schedules:
Every 3 hours: Reviews all exceptions created within the last 24 hours.
Every 24 hours: Reviews all exceptions older than 24 hours.
During these reviews, the system evaluates active exceptions against a growing library of resolution rules.
Default Rule: Resolves exceptions that have been open beyond a user-defined threshold, preventing stale exceptions from cluttering workflows.
Public Rules: Maintained by Pipe17 and updated regularly to reflect app and integration changes. These rules target common scenarios where exceptions can be automatically resolved.
Availability
New organizations: The Resolution Engine is enabled automatically—no setup is required.
Existing organizations: The feature is being rolled out progressively and may not yet be active in all accounts.
Access: When available, navigate to app → Automations → Exceptions → Scheduled Rules.
Available Scheduled Rules
Rule Name |
What It Resolves |
When It Applies |
|---|---|---|
Resolve Exceptions by Days Since Created |
Exceptions that remain open beyond a specified number of days |
Automatically resolves after a user-defined time threshold (e.g., 40 days). Cannot be disabled or deleted. |
Resolve Fulfillment Exceptions if Acknowledged |
Fulfillment exceptions initially blocking orders |
Once the update has been successfully acknowledged by the sales channel. |
Resolve Exceptions if the Integration is Connected |
Unexpected Disconnect exceptions |
When the integration status returns to Connected. |
Resolve Exceptions if the Integration is Disabled |
Exceptions related to disabled integrations |
Immediately upon the integration being turned off. |
Resolve Exceptions on Inactive Orders |
Exceptions tied to canceled, archived, closed, or deleted orders |
Once the order moves into one of these inactive statuses. |
Resolve Exceptions for Canceled Shipping Requests |
Exceptions linked to canceled or canceledRestock shipping requests |
Once the shipping request is marked as canceled. |
Resolve Stuck Order Exceptions When Orders Are Sent to Fulfillment |
Stuck order exceptions |
Once the order is successfully sent to fulfillment, confirming progress. |
You can enable or disable each rule (except the default Resolve Exceptions by Days Since Created rule) and edit the rules to meet the needs of your operation in the dotted menu.
Need Help?
If you need additional assistance:
Use Ask Pippen, our AI agent, located at the top of the app 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.
Comments
0 comments