Service Status

When To Use The Status Page

Open the Senler status page when the same problem affects several users or different sections fail at the same time. The page is public and does not require cabinet sign-in.

You can also open it from “Status” in the website's top menu. The indicator beside the menu item shows the overall status.

For an error limited to one project, channel, or action, use the project's event history and background processes. The general status page does not show a specific project's settings.

What The Page Shows

The top of the page shows the overall Senler status, its update time, and the number of features with a known status. Individual groups and features appear below. Data refreshes automatically; the “Refresh” button requests an update manually.

“Operational” means the available checks have not detected a failure. “No data” means there is not enough current information: it confirms neither normal operation nor an outage. Check the feature you need as well as the overall status.

Example current statuses: overall status, update time, and availability of individual features. This is an illustration, not live service data.

History And Incidents

The history period can be switched between 24 hours, 7 days, and 30 days. Timelines show changes in individual feature status, with the time up to which history has been loaded. Unknown intervals count as neither normal operation nor downtime; some intervals may have no data while history is loading.

History period and service timelines: colors show status, while a grey segment means no data.

The Problem periods section groups intervals when Senler's overall status indicated a failure and shows affected services. A short problem with an individual feature may appear on its timeline without appearing in this list. An absence of entries therefore does not mean every feature worked without errors.

The period status explains the current situation:

Ongoing means there is evidence of a continuing problem.
Partially recovered means some affected services are working again, but problems remain.
Recovered means recovery is confirmed for the overall state and affected services.
Recovery not confirmed means there is not enough data. It does not assert that the failure is still happening.

The card separates services with ongoing problems, recovered services, and services without recovery data. Expand Recovered services, then the service you need to see its episodes and the time its operation was confirmed.

Durations are shown separately for outages, major problems, and individual problems. If there are multiple intervals, select Show intervals. Time without observations is not included in failure duration.

Example problem period: some services have recovered, while others show ongoing problems or lack confirmed recovery.

If history for the selected period cannot be loaded temporarily, current statuses remain available.

Confirmation of operation may arrive after a gap without data. The page then shows when operation was confirmed and states that the exact recovery time is unknown. The gap itself remains unknown. If data covers only part of the period, a statement that no problems were recorded applies only to that available part of history.

If Overall Status Is Normal

Open History to check messages, agent starts, tools, and delivery. For an import, migration, channel refresh, or another long-running operation, open Processes. This separates a general service incident from an error in a specific setting or operation.