Marking as P1 as this has serious usability implications.

This also causes sheriff-o-matic to not show any failures once in a while.

Snoozing also does not work due to this error.

oops this looks like a client-side error, not a 404.

Which tree did this happen on? Are there any more details you can remember about the type of alert you were trying to link a bug to? (ie: group or not group?)

At the moment, I can't seem to replicate this problem with any of the alerts on Sheriff-o-Matic, so I wonder if this might be something that happens sporadically. 

This happens in Chromium tree. Here's the same error that's persistently on the page. Do you see it?

Deleted: Screenshot from 2017-10-24 12:25:11.png 43.0 KB

	Screenshot from 2017-10-24 12:25:11.png 43.0 KB View Download

Weird, I cannot repro this on staging even though it's now running 12307-d65cf28 (same rev as prod). Link bug, snooze etc work as expected.

Is there anything in the dev tools network panel about 403s or other error responses?

The errors are gone for me now, but I do see a 404 that appears harmless.

GET https://sheriff-o-matic.appspot.com/api/v1/logdiff/ 404

Are you still seeing this error?

Seems fine now, thank you.

I believe this is related to a flaky error where Sheriff-o-Matic sometimes fails to fetch annotations. I've observed this happening since we added alert splitting.