Check and fix your account's integration
Read an account's Integration tab, fix a run blocked by changed credentials, test them, and request an extraction.
Chapters
Transcript
In this video, we'll check an account's integration, and fix it when it stops working. Open the account, and go to the Integration tab. It lists every run Routy made, newest first. The badge beside the tab shows how the newest run ended. Completed means the run collected what it set out to. Skipped means there was nothing to do. It is not a failure. Failed with this message is a problem on our side. It is retried automatically, and no action is needed. Blocked is the one that needs you. Nothing more is collected until it is fixed. Here the program refused the sign-in. Usually that means your password or API key changed. Click Edit, then the Integration step. Test Integration signs in with the credentials Routy has saved. It fails, with the program's own reason. So the saved key is no longer good. Click the pencil on the API key, and paste the new one from the program. Then test again. This time it tests what you just entered, before anything is saved. It works, so click Save. Saving new credentials starts a run straight away, to fill in what the blocked runs missed.
Refresh the page after a moment, and the run is at the top, marked Credentials Changed.
A few minutes later, it has completed. That also closes the issue the blocked run raised. Extract collects a date range now, instead of waiting for the next scheduled run. Use it when you know dates are missing. You can go back up to a hundred and twenty days. Dates that already have data are left out. That's it. The help panel on this screen explains every status, and what to do about each one.