Account integration failed
A scheduled run for one of your accounts stopped before it collected anything, for a reason that does not fit any of the more specific sign-in or credential issues.
What it means
Routy signs in to each affiliate program on a schedule and collects your stats. This run ended without collecting. Until a run completes, the account's numbers stop updating.
The message on the issue starts with "Account integration failed:" and then gives the reason the run stopped. That reason is the most useful part, so read it first.
Why it happens
The causes we see most often, in order:
- Your master password is not active. The message reads "Master password is required for this account". The account signs in with a saved password, and Routy cannot unlock saved passwords until someone on your team enters the master password.
- A saved value is in the wrong format for this program. For example, "Username must be an email": some programs only accept the email address you log in with, not a short username.
- A setting the program needs is missing. The message reads "Missing required settings:" followed by the setting's name.
What you can do
- Open the issue's details and read the message after "Account integration failed:".
- If it says the master password is required, open Settings, go to the master password panel and choose Enter master password. Anyone on your team who knows it can do this. See Master password.
- If it names a value in the wrong format, open Accounts, click the account, click Edit, go to the Integration step, and correct the value. Click Test Integration, then Save. See Your account's integration.
- If it names a missing setting you don't recognise, or the message doesn't match any of the above, contact support with the account name and the exact message.
Saving new credentials starts a run straight away.
When it clears
It closes by itself on the account's next run that completes. If no run hits the same failure for 24 hours, it also closes on its own. You can press Resolve yourself, but if the problem is still there the next run opens it again.