Troubleshoot the Productboard connector
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Productboard from the Previews page. See Manage Databricks previews.
Resolve authentication, access, not-found, invalid-request, rate-limit, and retry errors from the managed Productboard connector in Lakeflow Connect.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
When Productboard returns an error detail, the pipeline shows that detail. Otherwise, it shows the message listed in each section.
Pipeline fails to authenticate
Error message:
Authentication failed. Credentials are missing or invalid.
Cause: Productboard rejected the access token. The connector requests a new token and retries automatically, so this error persists only when the connection credentials are not valid.
Solution:
Confirm that the Client ID, User Email, and Private Key on the connection match the Productboard OAuth application, and that the private key includes its BEGIN and END lines. The user email must belong to an activated user in the application's workspace. See Configure authentication to Productboard and Create a Productboard connection.
Pipeline fails with an access denied error
Error message:
Access denied. You do not have permission to perform this operation on the requested resource.
Cause: The OAuth application or the user that the connector signs in as doesn't have access to the data for a selected table.
Solution:
Confirm that the OAuth application has the required read scopes and that the user has access to the data. See Required OAuth permissions.
Pipeline fails because a resource is not found
Error message:
The requested resource could not be found or you do not have permission to access it.
Cause: Productboard returns the same response when a resource doesn't exist and when the caller can't access it.
Solution:
Confirm that the user that the connector signs in as has access to the data for every selected table, then rerun the pipeline.
Pipeline fails with an invalid request error
Error message:
Invalid request. The request is malformed or missing required parameters.
Cause: Productboard rejected a request. One common cause is a start_datetime value that isn't in yyyy-MM-ddTHH:mm:ssZ format.
Solution:
Check the start_datetime value in the pipeline's source_configurations. See Connector options.
Pipeline is rate limited
Error message:
You have exceeded the allowed number of API requests. Please wait before making additional requests.
Cause: Productboard limits API requests to 50 per second for each access token. The connector waits for the interval in the Retry-After response header, then retries. For more information, see Rate limits in the Productboard developer documentation.
Solution:
Reduce how often the pipeline runs, or avoid running other integrations that use the same Productboard user at the same time.
Pipeline fails after retries
Error message:
Request failed after retries. Please wait a few minutes and run the pipeline again.
Cause: Productboard returned a timeout or server error, and the connector's automatic retries didn't succeed.
Solution:
Wait a few minutes, then rerun the pipeline.