@William_Green, One thing that comes to mind is that you failed to store the newly issued refresh token when you called the API to refresh authorization. I am seeing a high number of requests yesterday morning to refresh access tokens that are issued to your application. This looks pretty atypical compared to requests you’ve made in the past to refresh authorization.
Yesterday you had 82 refresh requests. 23 failed and 59 succeeded. On Monday you only had 1 refresh request which closely aligns with previous weeks.
Something to note: if you call the API to refresh authorization you should get back a new access token and refresh token pair. That previously issued refresh token that you had stored should still be valid and should give you back the current access token and refresh token pair. Once you use the latest refresh token to obtain a new access token and refresh token pair then the refresh token was issued two times ago will be invalidated.
If you have a “stale” refresh token then unfortunately the user will be required to reauthorize your application. A stale refresh token can also occur if the user revokes authorization to your application on dwolla.com. This is unlikely but can occur so I wanted to point it out.