Troubleshooting

This page contains a list of common errors and known issues encountered while integrating PagerDuty with Zluri, and instructions on how to fix them.

If your issue isn’t mentioned here, feel free to submit a ticket or contact us directly at [email protected].

PAG-100-A: The apiKey used to connect this integration is invalid

This error occurs while connecting PagerDuty to Zluri with an invalid API key.

To resolve this error:

  • Ensure you are generating the API key correctly in PagerDuty:

    1. Go to PagerDutyConfigurationAPI Access
    2. Click Create New API Key
    3. Provide a meaningful description for the key
    4. Copy the generated API key immediately (it won't be shown again)
  • Verify that you are copying the API key correctly:

    • Copy the entire key without any extra spaces or characters
    • Ensure no characters are missing from the beginning or end
    • The key should be pasted exactly as generated

After generating a new API key, try to connect the integration again.

PAG-100-B: The apikey used for this integration is expired/revoked

This error occurs when the API key used to connect PagerDuty to Zluri has expired or been revoked.

Common causes include:

  • The API key was manually deleted from PagerDuty
  • The user who created the API key was deactivated
  • API key rotation policies caused the key to expire
  • Admin settings changed to revoke existing keys

To resolve this error:

  1. Go to PagerDutyConfigurationAPI Access
  2. Check if your existing API key is still listed and active
  3. If the key is missing or inactive, create a new API key
  4. Use the new API key to reconnect the integration in Zluri

PAG-101-A: The user trying to connect the integration does not have sufficient permissions to access users

This error occurs when the PagerDuty user does not have the necessary privileges to access user information.

To resolve this error, ensure the user has one of the following roles:

  • Account Owner
  • Admin
  • Global Admin
  • Manager (with appropriate permissions)

Additionally, verify that:

  • The user can access the Users section in PagerDuty
  • The account has the necessary plan that includes user management features
  • No custom role restrictions are blocking user data access

After updating the permissions, try to connect the integration again.

PAG-101-B: The permission for the user who connected the integration is modified/revoked

This error occurs when the PagerDuty user who connected to Zluri has lost the required permissions to access users.

To resolve this error:

  1. Verify the original user still has appropriate permissions:

    • Account Owner
    • Admin
    • Global Admin
    • Manager (with user access)
  2. Check if the user's role was modified or downgraded

  3. Ensure the user can still access the Users section in PagerDuty

  4. After restoring the appropriate permissions, reconnect the integration

PAG-102-A: Your account is not associated with any users

This error occurs when the PagerDuty account being connected has no users associated with it.

To resolve this error:

  • Verify that users exist in your PagerDuty account
  • Check that you're connecting the correct PagerDuty account/subdomain
  • Ensure users haven't been accidentally removed or deactivated
  • If this is a new account, add at least one user before connecting

PAG-102-B: Your account is not associated with any users. To proceed, please reconnect the integration with an account that has one or more users

This error occurs during sync when the connected PagerDuty account no longer has any users.

To resolve this error:

  1. Add users to your PagerDuty account, or
  2. Reconnect the integration using a different PagerDuty account that contains users
  3. Verify the account has active users before reconnecting

PAG-104-A: The user trying to connect the integration does not have sufficient permissions to access logs

This error occurs when the PagerDuty user cannot access session logs or user activity data.

To resolve this error:

  • Ensure the user has Admin or Account Owner privileges
  • Verify that the PagerDuty plan includes access to session/activity logs
  • Check that no custom restrictions are blocking log access
  • Confirm the user can view the Analytics or Reporting sections in PagerDuty

PAG-104-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission to access logs and reconnect the integration

This error occurs when the user who connected the integration has lost permissions to access logs.

To resolve this error, restore the necessary permissions and reconnect the integration.

PAG-105-A: The user trying to connect the integration does not have sufficient permissions to access audits

This error occurs when the PagerDuty user cannot access audit records.

To resolve this error:

  • Ensure the user has Admin or Account Owner privileges
  • Verify that your PagerDuty plan includes audit log features
  • Check that audit logging is enabled in your account settings
  • Confirm the user can access ConfigurationAccount SettingsAudit Trail

PAG-105-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission to access audits and reconnect the integration

This error occurs when the user who connected the integration has lost permissions to access audit records.

To resolve this error, restore the necessary audit permissions and reconnect the integration.

PAG-106-A: The user trying to connect the integration does not have sufficient permissions to access logEntries

This error occurs when the PagerDuty user cannot access incident log entries.

To resolve this error:

  • Ensure the user has appropriate incident management permissions
  • Verify the user can view incident details and activity logs
  • Check that the user has at least Manager role or higher
  • Confirm access to the Incidents section in PagerDuty

PAG-106-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission to access logEntries and reconnect the integration

This error occurs when the user who connected the integration has lost permissions to access incident log entries.

To resolve this error, restore the necessary incident access permissions and reconnect the integration.

PAG-107-A: The user trying to connect the integration does not have sufficient permissions to access licenses

This error occurs when the PagerDuty user cannot access license information.

To resolve this error:

  • Ensure the user has Admin or Account Owner privileges
  • Verify that license management is available in your PagerDuty plan
  • Check that the user can access billing and subscription information
  • Confirm access to ConfigurationAccount SettingsPlan & Billing

PAG-107-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission to access licenses and reconnect the integration

This error occurs when the user who connected the integration has lost permissions to access license information.

To resolve this error, restore the necessary billing/license permissions and reconnect the integration.

PAG-108-A: The user trying to connect the integration does not have sufficient permissions to access licenseAllocations

This error occurs when the PagerDuty user cannot access license allocation details.

To resolve this error:

  • Ensure the user has Admin or Account Owner privileges
  • Verify access to user license management features
  • Check that the user can manage user assignments and roles
  • Confirm the PagerDuty plan includes license allocation management

PAG-108-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission to access licenseAllocations and reconnect the integration

This error occurs when the user who connected the integration has lost permissions to access license allocations.

To resolve this error, restore the necessary license management permissions and reconnect the integration.


If your issue is not listed here, please contact Zluri support with the error details for further assistance.