Bad Gateway causes failure to retrieve _all_ statuses about mastodon-archive HOT 7 CLOSED

from mastodon-archive.

from mastodon-archive.

From a user perspective:

The error could either be more detailed -- for example, what site gives a bad gateway, what post was it accessing, etc. -- give me information to debug it / contact the owner.

The alternative of saving the partial result or skipping that specific message / favourite is also important as otherwise you're sacrificing the entire history (which in my case is 1 or 2 years worth) for one bad / offline site.

from mastodon-archive.

from mastodon-archive.

That's the thing. The instance I use was up and responding to requests at the time of the failure. I've contacted the instance admin to see if there's something I or they need to do to solve it.

Previously I figured the 'statuses' grabbed both interaction statuses as well as your own statuses, so it was a fair assumption to allow skipping of foreign statuses that we can't grab (for whatever reason -- but most likely because the instance is dead (see: the death of witches.town) or otherwise non-responsive (down for maintenance)).

from mastodon-archive.

Thanks for the explanation. I've started talking to the server admin, we dug into it and it was a database timeout.

from mastodon-archive.

Phew! 😅

from mastodon-archive.