This article will guide you through simple steps to understand why some of your companies' data connections may be pendingAuth.
Audience
This article is aimed at Codat portal users with Admin, Developer or Analyst roles, or any user who wants to understand why a data connection is not in a Linked status.
Pre-requisites
To follow this guide, you must be a Codat portal user.
Understanding why a data connection is 'pendingAuth'
The first status of a newly created data connection is pendingAuth.
Data connections remain pendingAuth until the end-user completes the link flow.
While most of the cases of non-Linked connections may be due to the end-user abandoning the flow (eg. closing the window browser, unstable network connection, etc.), some pendingAuth connections can be explained by an error downstream.
An error downstream is typically an error that the underlying platform has returned to Codat during the linking process.
When this happens, you can access more information by logging into the Codat portal and hovering over the company that you are interested in.
Click on the Connections icon as shown below:
Navigate to the Errors sections. Each attempt to link that resulted in an error gets its own section that should provide more information about the error that resulted in the data connection remaining pendingAuth:
------------------------
If you have any questions on the information shared above, contact support@codat.io.