Page 1 of 1
unable to update collection - 'Character not found'
Posted: October 1st, 2018, 2:22 am
by Kionine
I am unable to update my collection.
When I try to update, I get a 'Character not found' message. If I use the link supplied in the error message, my characters armory page opens up without problems.
It looks like a bug.
Regards
Kio
Re: unable to update collection - 'Character not found'
Posted: October 1st, 2018, 2:46 am
by Avalee
Same here.
Re: unable to update collection - 'Character not found'
Posted: October 1st, 2018, 2:52 am
by Lornaa
Same here, just went to update and getting the same "character not found" message
Re: unable to update collection - 'Character not found'
Posted: October 1st, 2018, 2:55 am
by Gunmarie
Same here
Re: unable to update collection - 'Character not found'
Posted: October 1st, 2018, 10:17 am
by Kionine
Quick update.
I can update now, but I am missing 150'ish pets.
Edit: I've tried updating a few more times, and each time it shows a different number of pets
Re: unable to update collection - 'Character not found'
Posted: October 1st, 2018, 11:15 am
by Lornaa
I've just updated and lost over 100+ pets...
Re: unable to update collection - 'Character not found'
Posted: October 1st, 2018, 12:36 pm
by Eggs
Lornaa wrote:I've just updated and lost over 100+ pets...
I updated and now i have 1 pet
Re: unable to update collection - 'Character not found'
Posted: October 2nd, 2018, 1:47 am
by Lornaa
I updated earlier and went down to 3 pets, then back up to 923 and it's just dropped me back down to 864. Can anyone please let us know what's happening???
Re: unable to update collection - 'Character not found'
Posted: October 2nd, 2018, 2:51 am
by Quintessence
It appears that the Blizzard API is experiencing some technical difficulty lately. This can cause an error when attempting to re-import your collection to WarcraftPets, or even cause a drop in your "total unique pets" count on this site.
From the API Bnet Forums:
https://us.battle.net/forums/en/bnet/topic/20769387154
https://us.battle.net/forums/en/bnet/topic/20769387142
We'll have to wait for Blizzard to fix this issue on their end. Apologies for the inconvenience.