Return to Question

I'm again looking at rene's SEDE query Status of the SEDE Refresh on Sunday 03:00 UTC to check the status, which is currently (in part):

... which is about 10 hours before I write this. I do hope nothing is -- or was -- on fire!

This particular problems seems to be DISTINCT from the most recent issue of a failure on a backup share that caused the process to be disabled, since there's evidence of previous restoration activity:

I'm again looking at rene's SEDE query Status of the SEDE Refresh on Sunday 03:00 UTC to check the status, which is currently (in part):

... which is about 10 hours before I write this. I do hope nothing is -- or was -- on fire!

This particular problem seems to be DISTINCT from the most recent issue of a failure on a backup share that caused the process to be disabled, since there's evidence of previous restoration activity:

I'm again looking at rene's SEDE query Status of the SEDE Refresh on Sunday 03:00 UTC to check the status, which is currently (in part):

... which is about 10 hours before I write this. I do hope nothing is -- or was -- on fire!

This particular problems seems to be DISTINCT the most recent issue of a failure on a backup share that caused the process to be disabled, since there's evidence of previous restoration activity:

I'm again looking at rene's SEDE query Status of the SEDE Refresh on Sunday 03:00 UTC to check the status, which is currently (in part):

... which is about 10 hours before I write this. I do hope nothing is -- or was -- on fire!

This particular problems seems to be DISTINCT from the most recent issue of a failure on a backup share that caused the process to be disabled, since there's evidence of previous restoration activity: