Confusion on "Not all systems operational" about cf-workers-status-page HOT 6 CLOSED

Nice! Glad it works now! :) I will take a look into the GC script, so the first issue will be eliminated automatically :)

from cf-workers-status-page.

Hello @ramithuh, seems there are a couple of monitors in your state that were not operational and didn't get cleaned up correctly once you removed them from your config.
For example rotaractmora-manusath-contrib-portal

What version of the Status Page are you using? Some garbage collection was refactored in the latest version (https://github.com/eidam/cf-workers-status-page/releases/tag/v1.2.0)

from cf-workers-status-page.

I'm using the latest version 😃,
I just edited the lastUpdate's all operational to true.. wonder why these two entries don't have detailed info

Update 1: lastupdate went to all operational=false again
Update 2: I cleared those two entries completely.. however it seems that the first test results in 301 & 302

from cf-workers-status-page.

One thing to note, KV takes a while to propagate to all datacenters, so your change might have been overwritten by the CRON before it reached the dc it's running in

from cf-workers-status-page.

You also need to specify the URL that returns the expected code or set followRedirect to true.

It's by default disabled as redirect counts toward fetch() limit in Workers (50)

from cf-workers-status-page.

Thank You for your help!,
I tried editing the two fields and now it seems to work.. https://status.rotaract.social

from cf-workers-status-page.