# Analyzing permission dependency cycle trace telemetry
> APPLIES TO: Business Central 2022 release wave 1 and later
A permission dependency cycle occurs when a permission set depends on itself, which can happen when you build permission sets that include other permission sets. For example, suppose you create a permission set Y that includes permission set X. If you then try to modify permission set X to include permission set Y, you create a dependency cycle. When you create a permission dependency cycle in the Business Central client, you get an error similar to the following message:
The permission set [XX] has a circular reference on path [XX]->[YY]->[XX].
This telemetry data lets you identify and analyze permission problems that users might experience in Business Central.
## Dependency cycle discovered in permission sets
Occurs when a permission set dependency cycle is logged while permission sets are expanded or validated.
### General dimensions
Dimension|Description or value
message|Dependency cycle discovered in permission sets.
severityLevel|3
### Custom dimensions
Dimension|Description or value
eventId|RT0032
aadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.
alObjectId|Specifies the ID of the AL object in the current execution context. This value doesn't identify a permission set in the cycle.
alObjectName|Specifies the name of the AL object in the current execution context.
alObjectType|Specifies the type of the AL object in the current execution context.
alStackTrace|The stack trace in AL.
clientType|Specifies the type of client that opened the session, such as Background or Web. For a list of the client types, see ClientType Option Type<../developer/methods-auto/clienttype/clienttype-option>.
companyName|The current company name.
component|Dynamics 365 Business Central Server
componentVersion|The version number of the component that emits telemetry (see the component dimension)
environmentName|The name of the tenant environment. This dimension isn't included for Business Central on-premises environments. See Managing environments<tenant-admin-center-environments>.
environmentType|The environment type for the tenant, such as Production, Sandbox, Trial. See tenant-admin-center-environments#types-of-environments.
permissionSetCycle|The dependency path of the permission sets in the cycle. Long paths are truncated in the middle to retain the start and end of the cycle.
telemetrySchemaVersion|The version of the Business Central telemetry schema.
## Related information
Composing Permission Sets<../developer/devenv-permissionset-composing>
../developer/devenv-upgrading-extensions
Monitoring and Analyzing Telemetry<telemetry-overview>
Enable Sending Telemetry to Application Insights<telemetry-enable-application-insights>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-permission-dependency-cycle-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-permission-dependency-cycle-trace/
