You might have inadvertently caused this situation by issuing the “my access token” or vice-versa. Ultimately, there can be only one representation of your authorization with an application – in most circumstances, if you complete an authorization flow for the same level of permissions for a token that already exists, you’ll get the same set of strings back to represent that permission. But there are cases where either a revocation has occurred or the level of permissions being asked for is different, and in these cases new strings for the oauth_token and oauth_token_secret will be issued, invalidating previous representations.