Upcoming

One forward-looking list of everything Enori knows is going to happen to your monitors, your maintenance schedule, your reports and your account — sorted by how soon.

What it is

Most of Enori answers "what happened?" — incidents, alerts, uptime, the timeline. Upcoming answers the other question: "what's about to happen, and how long have I got?"

It is a projection, not a to-do list. Nothing is stored for it and nothing is scheduled by it. Every row is read live from something you already configured — a certificate's expiry date, a cron expression, a maintenance window, a snooze you set, a report you scheduled, your trial end date — and rendered on one timeline.

You'll find it in two places:

The panel's "View all N →" link takes you to the full page.

The seven categories

Every row belongs to one of seven categories. Nothing else appears here.

A few of these have rules worth knowing:

Scheduled run only covers Job monitors that run daily or less often, and only while the monitor is active. A job that fires every five minutes is a heartbeat, not something you plan around — listing it would push everything else off the page, and it would always be the most urgent thing there. For minute-by-minute Job history, use the Jobs overview and the monitor's own detail page. Paused Job monitors are left out too: there is no next run to wait for.

Maintenance treats recurring and one-off windows differently. A recurring window (daily, weekly, monthly) shows its next occurrence anywhere in your horizon. A one-off window only appears when it's within 7 days — a single window you booked for four months out isn't something you need reminding of today, but the one on Thursday is.

Report delivery shows active schedules only. If a schedule was switched off — by you, or automatically because your plan no longer includes scheduled reports — it has no next delivery to show.

Subscription covers four dates, and each one only appears when it actually applies:

You will not see a "Subscription renews" row for a normal, healthy subscription. It renews quietly; there's nothing for you to do, so there's nothing to warn you about.

The three urgency bands

Rows are grouped into three bands and sorted by urgency first, then by date. A maintenance window in 3 days always sits above a certificate expiring in 40, whatever their categories.

Later has no fixed end. It runs to whatever horizon you've selected — so at a 1-year horizon it holds events up to 365 days out. The band headers tell you the actual range each time; they're not fixed labels.

A band with nothing in it is hidden entirely, rather than shown with a zero.

Choosing how far ahead to look

On the full page, the pills above the list set the horizon:

The horizon changes what's fetched, not just what's displayed — pick 1 year and you'll see renewals the 90-day view genuinely didn't know about.

The dashboard panel is fixed at 90 days. Only the full page has the control.

Reading the badge on the right

Each row ends in a small badge. There are three forms:

Why maintenance gets a date and nothing else does. When you're more than a week from a maintenance window, "in 23d" is a number you have to do arithmetic on. The actual date is what you compare against your own calendar. Everything else — certificates, domains, job runs, snoozes, billing — is about how much time is left, so it stays relative.

in 0d should never appear. An event 23 hours away is shown as in 23h, not rounded down to zero days. If you ever see in 0d, that's a bug worth reporting.

Maintenance dates are shown in the window's own time zone — the one you picked when you created it — not in UTC and not in your browser's zone. If you scheduled "Sunday 02:00, Pacific/Auckland", this page says Sunday, and so does the Maintenance page. The two never disagree about the day.

All the timing is computed on Enori's servers, once per request. Your device's clock, and whether the tab has been open for six hours, don't affect the numbers.

Client mode (Business plan)

If you're on Business and using client mode — the tag switcher on your dashboard — the Upcoming panel is scoped to that client's monitors, and clicking "View all" carries the scope through to the full page. You'll see the tag as a chip next to the heading, so it's always visible why the list is shorter than usual.

Two things change under a scope:

• Maintenance rows describe only the monitors you can see. A window covering five monitors with just one in the current scope names that monitor, rather than reading "5 monitors" — a client-scoped screen shouldn't count monitors outside that client. If a window's monitors are all outside the current scope, the row says "No monitors in view" rather than pretending the window is empty.
• Subscription rows are hidden entirely. Your trial end date and your billing period are your account's business, not a per-client fact, so they're left out of a scoped view. Drop the scope to see them again.

Client mode is a Business-plan feature. On Base and Pro the switcher is unavailable and the feed is always your whole account.

Staying up to date

The list updates itself. When you create, edit or delete a maintenance window — or when one starts or ends on its own schedule — and when a snooze changes, the page refreshes on its own. There's no polling and no refresh button to hunt for.

Two things are worth setting expectations on:

• Not every category pushes. Certificate and domain expiry dates are refreshed by Enori's background checks, so a newly-read expiry appears on your next visit rather than the instant it's discovered. Nothing here is time-critical to the second — these are dates weeks away.
• Responses are cached briefly. A maintenance or snooze change you make clears the cache as it's announced, so your own next load is current. A different tab or device refreshing at that exact moment can still read an up-to-a-minute-old copy.

Very large accounts

The feed is capped at 500 events per response. Most accounts never come near it — but a large one can: a monitor can contribute three rows on its own (an SSL expiry, a domain expiry and a snooze), so 200 monitors with all three set is already past the cap, and a 365-day horizon is where that happens, because every annual domain renewal and every certificate falls inside it. Narrowing the horizon to 30 or 90 days is usually all it takes.

If you ever do exceed it, the cap is visible rather than silent: the counts at the top and on each band still describe your whole feed, so the numbers stay true even if the list below is shorter. And because the list is sorted by urgency, anything dropped is always the least urgent — never the thing you needed to see.

How this relates to the subscribed calendar feed

Enori's Timeline offers a subscribable calendar feed — an .ics URL you add to Google Calendar, Apple Calendar or Outlook so Enori's events appear alongside your own. See the Timeline guide for how to set it up.

These two surfaces are not the same set of events, and it matters. If you subscribe to the calendar specifically so you can stop checking a dashboard, you should know exactly what it will and won't tell you.

Only three things appear on both: certificate expiry, domain expiry, and maintenance windows.

Everything else on this page is absent from the calendar feed:

• Job next runs. The calendar does carry job events — but they are past executions, not the next scheduled run.
• Snooze resumes.
• Report deliveries.
• Every subscription deadline — trial ending, subscription ending, downgrade deadline, scheduled account deletion.

Read that last one twice if you're on a trial. Subscribing the calendar so you stop checking Enori is exactly the habit that causes a trial to end without warning: the one date you most needed is the one the calendar does not carry. Trial and billing deadlines live here, on this page, and in Billing — not on the calendar. Enori does email you a trial reminder as the trial nears its end, but the other three deadlines have no calendar entry at all.

In the other direction, the calendar carries plenty this page doesn't — incidents, alerts, configuration changes and job execution history — because those are records of the past and this page is only about the future.

Where each row takes you

Clicking a row goes to the place you'd actually fix or change the thing:

Reaching it from elsewhere

Upcoming is also available through the public API and the MCP server, so you can pull the same projection into your own tooling or ask an AI assistant about it.

• API: GET /api/calendar/upcoming?within= with an API key holding the monitors:read scope. within accepts 1 to 365.
• MCP: the get_upcoming tool, same horizon range.

Both return the same seven categories, the same three bands and the same server-computed timings as this page. The MCP tool is always account-wide — it has no client-mode scope equivalent.

Related

• Maintenance windows — creating the windows that appear here
• Reports — scheduling the report deliveries that appear here
• Timeline — the historical view, and the subscribable calendar feed
• Domain monitoring — the full domain-expiry warning ladder
• Website monitoring — certificate expiry monitoring
• Job monitoring — cron schedules and time zones
• Billing — trials, plan changes and downgrade deadlines