Auto-resolution

The platform can close incidents automatically when the condition that opened them clears — see Statuses and lifecycle for how automatic resolution works. Auto-resolution is driven by resolvers, each of which watches for one kind of recovery. This page covers how to turn resolvers on and off for your network. You manage this in Settings → Auto Resolvers.

​

Resolvers

A resolver watches for a specific recovery and, when every affected station on an incident has recovered, lets the incident close itself. The available resolvers include:

​

Turning a resolver off

Each resolver has an on/off toggle for your network. Turning one off does not stop the platform from tracking recovery — recoveries are still recorded on the incident’s roster — it just stops the incident from closing itself. The incident stays open for a Support Operator to review and close deliberately. Turn a resolver off when you want a human to confirm closure for that kind of incident rather than letting it resolve unattended; leave it on to let clean recoveries close without Support Operator effort.

​

Defaults and your override

Resolvers have a baseline setting managed by Nayax Energy Core. Your network’s toggle is an override on top of that baseline, and it wins for your network in both directions: you can turn a resolver off even if it is on by default, and you can turn one back on even if Nayax Energy Core has disabled it globally. When a resolver is disabled globally, the screen shows that, and turning it on re-enables it for your network only. Removing your override returns the resolver to the Nayax Energy Core-managed default.

Auto-resolution can only close incidents that are still in an early working state (NEW, INVESTIGATING, or MITIGATING). Once a Support Operator has moved an incident to WAITING_ON_OEM or POST_MORTEM, it will not auto-close regardless of resolver settings — see Statuses and lifecycle.