Setting up new OAuth 2.0 credentials can be a fickle process. For one, different OAuth providers may have unique or badly documented requirements for how you pass through your configuration. For another, there can be latency between publishing up a remote credential and it being available for use by consumers like Tines.

Now, for authorization_code grants, we surface the full error context we receive from the remote provider if anything goes wrong, making it much easier to debug issues.