Where issues come from and how they close automatically
Dozens of parts of the system create issues: order import, packing, carriers, automations, and marketplaces. Some close automatically when the cause is gone.
Step by step — check whether a problem keeps coming back
- Go to Tools → Issues.
- First change Status to All issues. The default Unresolved view hides exactly the entries you may need: ones closed manually even though the problem keeps returning.
- Find the issue by entering the object identifier (order number, EAN) in Search... (Q), or narrow the list with Source. > The Source filter shows only active integrations. Issues from a disabled integration will not appear there; use search instead.
- Click the row and check Occurrences in the panel.
1xmeans once;12xmeans a persistent repeat. - Check Status. Resolved with a high occurrence count is a common pattern: someone closed the issue, it came back, and it has been hidden from the default view ever since.
- Check Resolved by to see who closed it.
- Expand Technical details for the history of causes. This section appears only when there is something to show.
- Compare Created with Updated. A recent update date on an issue marked Resolved means the cause was not removed. Click Reopen and deal with it.
Who creates issues
Issues are created automatically in dozens of places. Common sources include:
| Area | Typical causes |
|---|---|
| Order import | Product not found, undeliverable address, invalid postal code |
| Packing | Carrier refused a label, response timed out, orphaned shipment |
| Carriers | Missing delivery-method mapping, shipment rejected |
| Automations | Rule action failed, event lost, rules entered a loop |
| Marketplace | Connector errors while pulling or pushing data |
| Stock | Ambiguous EAN, stock only partly uploaded |
Repeats do not create extra rows
The same problem on the same object does not create a new issue. It increments the occurrence counter and appends a cause to the history (up to five different causes are kept).
That makes the count column useful: 12x means a persistent repeat, not a one-off event.
Some issues close automatically
When the cause goes away — the address is corrected or the carrier finally accepts the shipment — the system closes the issue automatically and adds a clear automatic-resolution marker. It does not send a notification for this closure, to avoid messages about a problem that disappeared by itself.
Manual closure is final
Remember this asymmetry:
- an automatically resolved issue can reopen if the problem returns;
- an issue closed by a person is never reopened by the system.
If a problem returns after manual closure, you will see only the occurrence count increase and one update notification. The row stays marked resolved, so it will not appear in the default unresolved view.
This is a real operational trap: closing an issue because it “is not a problem right now” makes recurrences almost invisible. Close it only after the cause has been removed.
Some stock-related issues also have a 24-hour mute period before the same problem can be raised again.
Blocking issues
The model supports blocking issues that stop work on an order. In practice no process creates them today, so the blocking filter and card will show zero.
If one is created, note that resolving it does not automatically unblock the order — change the status manually.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo