[bug] Account migration to gts left some accounts stuck in follow requested

[kouya]

Describe the bug with a clear and concise description of what the bug is.

Some accounts after migration from mastodon 4.2.10 to gotosocial 0.16 show up as following on gotosocial but are on follow requested on mastodon's side.

What's your GoToSocial Version?

0.16.0

GoToSocial Arch

amd64 binary

What happened?

I migrated one of my accounts from mastodon 4.2.10 to gotosocial 0.16. There were two issues I noticed. The account had 678 followers, now after several days, 287 are still listed as following the old one and never transferred over. Some of those are normal because dead instances and they already followed the new account manually before. But some genuinely puzzle me, because they should have been moved.

1. There are about 100 accounts that just "ignored" the move. They are still following the old account and are happily alive and it seems strange they didn't move over at all. None of those have blocked or silenced the old or new server or vice versa as far as I can tell. And most are on software and versions that should normally support migration.

2. The second problem is more severe. There are accounts that count as following on gts' side but are on "follow requested" on mastodon's side. I have such an account myself, gts thinks it's following it, but on the account's side it is stuck on waiting for some confirmation and it doesn't receive posts from the new account.

Old account migrated from: https://botsin.space/@fennecbot New account moved to: https://icy.arcticfluff.eu/@fennecbot

This one https://botsin.space/@arcticfoxbot followed the old account and is now in that "limbo". Gts thinks it's following it, but the server it's running on is waiting for something.

I don't have too many logs from gts I could look into, I have all webserver access logs on the gts side from the day but it's a lot of noise in there. I can look up things in there if needed, just tell me what requests I should look up.

I'm also a little lost where the problem actually is, on gotosocial's or mastodon's side. Would also be interested if there is something that can be done (manually, hacky, etc) to fix it so that the instances from problem 2 will update their status to following.

What you expected to happen?

No response

How to reproduce it?

No response

Anything else we need to know?

No response