Failed to check if maintenance windows are active

Elastic Stack Kibana
,
1

After the update of the on-premises deployment, this error appears. What could be the root cause?

image
image469×162 10.7 KB

Untitled
Untitled1000×600 16.4 KB

1 Like
2

Hello @GiorgioS13

Could you please share when do you receive this error message, is it while accessing Kibana ?

As per the error message this seems to be related to “maintenance windows”

image
image193×202 5.67 KB

Can check Kibana Logs in order to understand more about the error.

What was your older version & current version of ELK ?

Thanks!!

3

Hello @Tortoise

Thank you for reply.

I noticed this issue when navigating to Security > Alerts.

The message states:
“Maintenance windows are a subscription feature.”

I do not have a subscription license.

The current version in use is 9.3.0.

4

Hi all,

We’re have the same error message on our 9.3.0 stack after upgrading from 9.2.4. Only shows up on the Security pages and Synthetics pages.

We also don’t have a subscription so accessing the Maintenance Window page simply asks if we’d like to trial or upgrade.

fetchResponse@https://{hostname}/30ab63cc0017/bundles/core/core.entry.js:1:244583

It’s not harming anything - but is annoying when it pops up over a button I’m about to click lol

There’s no related error message in the Kibana or Elastic logs - the closest message is this:

kbnode1  | [2026-02-11T11:48:40.643+00:00][ERROR][plugins.fleet.fleet:agent-status-change-task:1.0.2] [AgentStatusChangeTask] error: ResponseError: search_phase_execution_exception
kbnode1  |      Root causes:
kbnode1  |              script_exception: runtime error

But I have a feeling that might be completely unrelated?

Many thanks!

5

This seems to be a bug, have you reported it on Github already?

You should report there.

1 Like
6

As far as I have observed, it does not break anything and does not seem to have any impact however, I am still interested in understanding the root cause.

1 Like
7

Wow good shout, didn’t even check there.

There’s already a bug for it from December 2025

1 Like