[Bug]: Fresh import of backup file and new token for bank sync SimpleFin

Verified issue does not already exist?

• I have searched and found no existing issue

What happened?

Summary: Imported a backup of my budget into a fresh docker install within TrueNas. Cleared the SimpleFin token and entered in the New token created. Click Link accounts after token entry, button spins and prompts for me to enter in my token again.

I can confirm the token entered is not making a successful connection to SimpleFIn to change status to "Claimed". I have tested locally using SimpleFIn Developer and verified the token does work. I did attempt to unlink all accounts to see if re-link prompt would display with no luck

1. Initial thoughts are the token is still set to the prior token and as that's been "removed" it isn't changing the token to the new entered value

{
    "status": "ok",
    "data": {
        "error_type": "INVALID_ACCESS_TOKEN",
        "error_code": "INVALID_ACCESS_TOKEN",
        "status": "rejected",
        "reason": "Invalid SimpleFIN access token.  Reset the token and re-link any broken accounts."
    }
}

How can we reproduce the issue?

How can we reproduce the issue?

1. Docker installation
2. Import a backup file with a known token to have been removed from SimpleFin
3. Clear the token and enter in a newly created token
4. Spinning and re-prompt for token with below showing in Developer Tools

{
    "status": "ok",
    "data": {
        "error_type": "INVALID_ACCESS_TOKEN",
        "error_code": "INVALID_ACCESS_TOKEN",
        "status": "rejected",
        "reason": "Invalid SimpleFIN access token.  Reset the token and re-link any broken accounts."
    }
}

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Linux