I'm guaranteed this isn't user error, Considering that the recovery phrase was present in two distinct places: backed up within a file on S3, and printed on the bit of paper. Meticulously evaluation your recovery phrase for almost any typos or spelling mistakes. Even one slip-up can induce this error. https://e-bookmarks.com/story4468994/the-ultimate-guide-to-bip39-seed-phrase-github