Bug overview description.
I get the error message whenever I favorite art or animations-
Error: Unexpected error 5b7384c6c37a73daaedc5735a87eb8b9

Chrome Version 67.0.3396.62 (Official Build) (64-bit) on Windows 10 Home

What part(s) of the site page(s) are affected?
Artwork, browsing and adding any piece of art to a favorites lists triggers the error.

What is the expected behavior?
Should be able to add to a favorite without triggering.

What actual behavior is given instead?
The error code shows up on the top portion of the page.

Time of incident (if applicable).
16:53 MST

Can you reproduce the bug every time?
Yes, every time.

What steps did you take to replicate this bug?

Go to an animation, or still image you want to add and favorite it, error should appear.

Errors or other messages returned (if any).
No other errors.

Not entirely sure what the cause of this is, and I thought I'd report it here. Thank you.

This occurs for me too, but it does not prevent the post from being favorited. I'm using Safari on the iPhone.

I was able to fave several, then got the message. I was faved though after loading image again.

I'M using Firefox.

Right, I know the fave still "works" but why the error in the first place? Does it break anything else?

I am 90% sure this is due to ongoing site maintenance that started a few hours ago.

you get the same error when you remove a post from your favorites as well.

The redis server crashed or something. Our server birb has been notified.
Migration was occuring earlier so it might still be migrating?

Chaser said:
The redis server crashed or something. Our server birb has been notified.
Migration was occuring earlier so it might still be migrating?

Error is still occurring, unfortunately.

Well now I feel like a derp for reporting it >.>

The machine that this background task was running on was having continued networking problems and has been moved to a new machine. Error messages and timeouts should no longer be happening.

KiraNoot said:
The machine that this background task was running on was having continued networking problems and has been moved to a new machine. Error messages and timeouts should no longer be happening.

Ah, it fixed. I was wondering if these problems were just me. Thanks.