Troubleshoot the PagerDuty connector
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page describes common errors you might encounter with the managed PagerDuty connector and how to resolve them.
For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.
Pipeline fails with a missing-scope error
Error message:
Grant the following scope(s): <required_scopes> in your OAuth Application and re-run the pipeline again.
Cause: Your PagerDuty OAuth app does not grant every read scope that the selected tables require.
Solution:
Add the listed scopes to your PagerDuty OAuth app, then re-run the pipeline. For the scopes each table requires, see Required OAuth permissions.
Pipeline fails with an authorization error
Cause: The OAuth app or the account it belongs to does not have access to the requested resource. This might mean the account plan does not include the endpoint, or the app lacks the required scope.
Solution:
Confirm that your PagerDuty plan includes the resources you are ingesting and that the OAuth app grants the required read scopes. See Configure authentication to PagerDuty.
Pipeline is rate limited
Cause: The pipeline exceeded the PagerDuty REST API rate limit. PagerDuty returns HTTP 429 and reports the wait interval in the ratelimit-reset response header. For more information, see the PagerDuty REST API rate limits documentation.
Solution:
The connector automatically waits and retries when PagerDuty rate limits a request. If rate limiting persists, reduce how frequently the pipeline runs. See Ingest data from PagerDuty.
Pipeline fails to authenticate
Cause: The connection credentials are not valid, or the OAuth client secret has been rotated in PagerDuty.
Solution:
The connector refreshes the access token automatically. If authentication still fails, verify the Client ID, Client Secret, Service Region, and Subdomain on the connection. To update rotated credentials, see Create a PagerDuty connection.