{"title":"Telemetry event IDs in Application Insights","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-event-ids/","by":"JOP-AL","license":"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-event-ids, 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.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-event-ids","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn about the event IDs of Business Central events emitted to Azure Application Insights.","date":"2026-09-22","meta":{"topic":"article"},"outline":[{"level":1,"title":"Telemetry event IDs in Application Insights","slug":"telemetry-event-ids-in-application-insights","at":0,"chars":52055},{"level":2,"title":"Application events","slug":"application-events","at":171,"chars":4571},{"level":2,"title":"Client events","slug":"client-events","at":4742,"chars":407},{"level":2,"title":"Lifecycle events","slug":"lifecycle-events","at":5149,"chars":38427},{"level":2,"title":"Runtime events","slug":"runtime-events","at":43576,"chars":6873},{"level":2,"title":"Find AL event IDs in the application source","slug":"find-al-event-ids-in-the-application-source","at":50449,"chars":1306},{"level":2,"title":"Related information","slug":"related-information","at":51755,"chars":300}],"text":"# Telemetry event IDs in Application Insights\nThe following tables list the IDs of Business Central telemetry trace events that are emitted to Azure Application Insights.\n## Application events\nEvent ID|Area|Message\nAL0000LA2|Changelog configuration|Field added to changelog configuration<telemetry-changelog-configuration-trace#added>\nAL0000LA1|Changelog configuration|Field logging changed in changelog configuration<telemetry-changelog-configuration-trace#changed>\nAL0000LA3|Changelog configuration|Field removed from changelog configuration<telemetry-changelog-configuration-trace#removed>\nAL0000CTV|Email|Email sent successfully<telemetry-email-trace#success>\nAL0000CTP|Email|Failed to send email<telemetry-email-trace#failed>\nAL0000GKK|Email|Authenticated to SMTP server<telemetry-email-trace#smtp_auth>\nAL0000GKJ|Email|Connected to SMTP server<telemetry-email-trace#smtp_connection>\nAL0000GKL|Email|Email sent (using SMTP)<telemetry-email-trace#smtp_sent>\nAL0000CTE|Field monitoring|Sensitive field value has changed: {alfieldCaption} ({alFieldNumber}) in table {altableCaption} ({alTableNumber})<telemetry-field-monitoring-trace#changed>\nAL0000DD3|Field monitoring|Sensitive field monitor status has changed to {almonitorStatus}<telemetry-field-monitoring-trace#status>\nAL0000EMW|Field monitoring|Sensitive field added to or removed from monitor: {alfieldCaption} ({alFieldNumber}) in table {alTableCaption} ({alTableNumber})<telemetry-field-monitoring-trace#added>\nAL0000E2A|Permissions|User-defined permission set added: {alPermissionSetId}<telemetry-permission-changes-trace#setadded>\nAL0000E2B|Permissions|User-defined permission set removed: {alPermissionSetId}<telemetry-permission-changes-trace#setremoved>\nAL0000E28|Permissions|Permission set link added: {alSourcePermissionSetId} -> {alLinkedPermissionSetId}<telemetry-permission-changes-trace#linkadded>\nAL0000E29|Permissions|Permission set link removed: {alSourcePermissionSetId} -> {alLinkedPermissionSetId}<telemetry-permission-changes-trace#linkremoved>\nAL0000E2C|Permissions|Permission set assigned to user: {alPermissionSetId}<telemetry-permission-changes-trace#assigneduser>\nAL0000E2D|Permissions|Permission set removed from user: {alPermissionSetId}<telemetry-permission-changes-trace#removeduser>\nAL0000E2E|Permissions|Permission set assigned to user group: {alPermissionSetId}<telemetry-permission-changes-trace#assignedusergroup>\nAL0000E2F|Permissions|Permission set removed from user group: {alPermissionSetId}<telemetry-permission-changes-trace#removedusergroup>\nAL0000D3L|Retention Policy|Retention Policy Log Entry Logged: {alMessageType}<telemetry-retention-policy-trace#info>\nAL0000D6H|Retention Policy|Records Deleted Using Retention Policy: Deleted {alRecordsDeleted} records from Table {alTableNo}, {alTableName}<telemetry-retention-policy-trace#deleted>\nAL0000D6I|Retention Policy|First retention policy enabled on: {alCompanyName}<telemetry-retention-policy-trace#first>\nAL0000D6J|Retention Policy|Last retention policy disabled on: {alCompanyName}<telemetry-retention-policy-trace#last>\nAL0000I74|Azure Function Integration|Request sent to Azure function succeeded<telemetry-azure-function-integration-trace>\nAL0000I75|Azure Function Integration|Authorization failed to Azure function: {Function Host}<telemetry-azure-function-integration-trace>\nAL0000I7P|Azure Function Integration|Request sent to Azure function failed: {Function Host}<telemetry-azure-function-integration-trace>\nAL0000DHR|Performance Toolkit|Performance Toolkit run started.<telemetry-performance-toolkit-trace#started>\nAL0000DHS|Performance Toolkit|Performance Toolkit run finished.<telemetry-performance-toolkit-trace#completed>\nAL0000DHT|Performance Toolkit|Performance Toolkit run cancelled.<telemetry-performance-toolkit-trace#cancelled>\nAL0000DGF|Performance Toolkit|Performance Toolkit - {BCPT Header code} - {Scenario label} - {BCPT log entry status}<telemetry-performance-toolkit-trace#scenario>\nAL0000EIW|Onboarding|Onboarding Signal Started: {signal type}<telemetry-onboarding-trace#started>\nAL0000EIV|Onboarding|Onboarding Signal Completed: {signal type}<telemetry-onboarding-trace#CriteriaCompleted>\nAL0000O76|Financial Reports|telemetry-financial-report-usage-trace#financial-report-run-from-request-page-report-definition-code\nAL0000OKU|Financial Reports|telemetry-financial-report-usage-trace#financial-report-run-on-screen-report-definition-code\nAL0000QE9|MCP configuration|telemetry-mcp-configuration-trace#modified\nAL0000QEB|MCP configuration|telemetry-mcp-configuration-trace#deleted\nAL0000R0Q|MCP configuration|telemetry-mcp-configuration-trace#created\nAL0000R0R|MCP configuration|MCP default configuration designated<telemetry-mcp-configuration-trace#default>\n## Client events\nEvent ID|Area|Message\nCL0001|Page views|telemetry-page-view-trace#page-opened-alobjectname\nCL0002|Error message quality|User gave feedback on error message: [OK\\|Not OK]<telemetry-error-message-voting-trace>\nCL0003|Client action|Client action invoked:{Action}<telemetry-client-action-trace>\nCL0005|Control add-in|Exception raised inside a control add-in<telemetry-client-add-in-exceptions>\n## Lifecycle events\nEvent ID|Area|Message\nAL0000E24|Job Queue Lifecycle|Job queue entry enqueued: {alJobQueueId} <telemetry-job-queue-lifecycle-trace#enqueued>\nAL0000FNY|Job Queue Lifecycle|Job queue entry not enqueued: {alJobQueueId}<telemetry-job-queue-lifecycle-trace#enqueueError>\nAL0000E25|Job Queue Lifecycle|Job queue entry started: {alJobQueueId} <telemetry-job-queue-lifecycle-trace#started>\nAL0000E26|Job Queue Lifecycle|Job queue entry finished: {alJobQueueId} <telemetry-job-queue-lifecycle-trace#finishedrequest>\nAL000082C|Job Queue Lifecycle|JobID = {alJobQueueId}, ObjectType = {alJobQueueObjectType}, ObjectID = {alJobQueueObjectId}, Status = Finished, Result = Success, Company = {alJobQueueCompanyName}, Scheduled Task Id = {alJobQueueScheduledTaskId}<telemetry-job-queue-lifecycle-trace#finished>\nAL0000HE7|Job Queue Lifecycle|Job queue entry errored: {alJobQueueId}<telemetry-job-queue-lifecycle-trace#error>\nAL0000I49|Job Queue Lifecycle|Job queue entry rescheduled on login: {alJobQueueId} <telemetry-job-queue-lifecycle-trace#rescheduledOnLogin>\nAL0000JRG|Job Queue Lifecycle|Job queue entry {Job Queue Id} errored after {attempt number} attempts<telemetry-job-queue-lifecycle-trace#errorStopped>\nAL0000FMG|Job Queue Lifecycle|Running job queue once<telemetry-job-queue-lifecycle-trace#runOnce>\nAL0000KZV|Job Queue Lifecycle|Job queue entry cancelled: {job queue entry id}<telemetry-job-queue-lifecycle-trace#cancelled>\nAL0000E3F|Configuration Package|Configuration package export started: {packageSystemId}<telemetry-configuration-package-trace#exportstarted>\nAL0000E3G|Configuration Package|Configuration package exported successfully: {packageSystemId}<telemetry-configuration-package-trace#exportsuccessful>\nAL0000E3H|Configuration Package|Configuration package import started: {packageSystemId}<telemetry-configuration-package-trace#importstarted>\nAL0000E3I|Configuration Package|Configuration package imported successfully: {packageSystemId}<telemetry-configuration-package-trace#importsuccessful>\nAL0000E3N|Configuration Package|Configuration package apply started: {packageSystemId}<telemetry-configuration-package-trace#applystarted>\nAL0000E3O|Configuration Package|Configuration package applied successfully: {packageSystemId}<telemetry-configuration-package-trace#applysuccessful>\nAL0000E3P|Configuration Package|Configuration package deleted successfully: {packageSystemId}<telemetry-configuration-package-trace#deletesuccessful>\nAL0000EJ9|Extension Lifecycle|Upgrade tag searched for: {AlUpgradeTag}<telemetry-extension-update-trace#upgrade-tag-searched-for>\nAL0000FJ1|Cloud migration|telemetry-cloud-migration-trace#companion-table-repair-started\nAL0000FJ4|Cloud migration|telemetry-cloud-migration-trace#companion-table-repair-completed-successfully\nAL0000FXC|Cloud migration|telemetry-cloud-migration-trace#companion-table-repair-scheduled\nAL0000IGC|Cloud migration|Cloud migration has been disabled from company {companyname}<telemetry-cloud-migration-trace#cloud-migration-disabled>\nAL0000K0H|Cloud migration|telemetry-cloud-migration-trace#replication-run-completed\nAL0000K0I|Cloud migration|telemetry-cloud-migration-trace#replication-run-completed-with-failed-tables\nAL0000K0J|Cloud migration|telemetry-cloud-migration-trace#replication-run-started\nAL0000K0K|Cloud migration|telemetry-cloud-migration-trace#cloud-migration-data-upgrade-scheduled\nAL0000EJA|Extension Lifecycle|Upgrade tag set: {AlUpgradeTag}<telemetry-extension-update-trace#upgrade-tag-set>\nAL0000EIQ|User Checklist Lifecycle|User checklist status updated: {oldStatus} to {newStatus}<telemetry-user-checklist-trace>\nAL0000EIT|User Checklist Lifecycle|Checklist item status updated: {oldStatus} to {newStatus}<telemetry-user-checklist-trace>\nAL0000EIR|User Checklist Lifecycle|Checklist item status updated with guided experience item: {oldStatus} to {newStatus}<telemetry-user-checklist-trace>\nAL0000JT3|Feature Lifecycle|Feature switch has been flipped<telemetry-feature-management-trace>\nAL0000G7K|Feature Lifecycle|No telemetry logger has been registered for publisher {publisher}<telemetry-feature-telemetry#nologger>\nAL0000N0D|Report Layout Lifecycle|telemetry-report-layout-lifecycle-trace#report-layout-default-changed-by-user\nAL0000N0E|Report Layout Lifecycle|telemetry-report-layout-lifecycle-trace#report-layout-added-by-user\nAL0000N0F|Report Layout Lifecycle|telemetry-report-layout-lifecycle-trace#report-layout-deleted-by-user\nAL0000N0G|Report Layout Lifecycle|telemetry-report-layout-lifecycle-trace#report-layout-replaced-by-user\nAL0000N0H|Report Layout Lifecycle|telemetry-report-layout-lifecycle-trace#report-layout-properties-changed-by-user\nAL0000N0I|Report Layout Lifecycle|telemetry-report-layout-lifecycle-trace#report-layout-exported-by-user\nAL0000O77|Financial Report Lifecycle|Financial report definition created: {Report Definition Code}<telemetry-financial-report-lifecycle-trace#financial-report-definition-copied-report-definition-code>\nAL0000O78|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-definition-modified-report-definition-code\nAL0000O80|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-definition-deleted-report-definition-code\nAL0000OKX|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-definition-copied-report-definition-code\nAL0000ONR|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-definition-imported-report-definition-code\nAL0000ONR|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-definition-exported-report-definition-code\nAL0000O81|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-row-definition-created-row-definition-code\nAL0000O82|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-row-definition-modified-row-definition-code\nAL0000O84|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-row-definition-deleted-row-definition-code\nAL0000OKV|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-row-definition-copied-row-definition-code\nAL0000ONP|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-row-definition-imported-row-definition-code\nAL0000ONP|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-row-definition-exported-row-definition-code\nAL0000O85|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-column-definition-created-column-definition-code\nAL0000O86|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-column-definition-modified-column-definition-code\nAL0000O88|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-column-definition-deleted-column-definition-code\nAL0000OKW|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-column-definition-copied-column-definition-code\nAL0000ONQ|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-column-definition-exported-column-definition-code\nAL0000ONQ|Financial Report Lifecycle|telemetry-financial-report-lifecycle-trace#financial-report-column-definition-imported-column-definition-code\nLC0001|Company Lifecycle|telemetry-company-lifecycle-trace#company-created\nLC0002|Company Lifecycle|telemetry-company-lifecycle-trace#company-creation-canceled\nLC0003|Company Lifecycle|telemetry-company-lifecycle-trace#company-creation-failed\nLC0004|Company Lifecycle|telemetry-company-lifecycle-trace#company-copied\nLC0005|Company Lifecycle|Company copied canceled: {companyNameSource} to {companyNameDestination}<telemetry-company-lifecycle-trace#company-copy-canceled>\nLC0006|Company Lifecycle|telemetry-company-lifecycle-trace#company-copy-failed\nLC0007|Company Lifecycle|telemetry-company-lifecycle-trace#company-deleted\nLC0008|Company Lifecycle|telemetry-company-lifecycle-trace#company-deletion-canceled\nLC0009|Company Lifecycle|telemetry-company-lifecycle-trace#company-deletion-failed\nLC0010|Extension Lifecycle|Extension installed successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#installedsuccess>\nLC0011|Extension Lifecycle|Extension failed to install: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#installedfailed>\nLC0012|Extension Lifecycle|Extension synchronized successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}<telemetry-extension-lifecycle-trace#syncedsuccess>\nLC0013|Extension Lifecycle|Extension failed to synchronize: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#syncedfailed>\nLC0014|Extension Lifecycle|Extension published successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#publishedsuccess>\nLC0015|Extension Lifecycle|Extension failed to publish: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#publishedfailed>\nLC0016|Extension Lifecycle|Extension un-installed successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#uninstalledsuccess>\nLC0017|Extension Lifecycle|Extension failed to un-install: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#uninstalledfailed>\nLC0018|Extension Lifecycle|Extension unpublished successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#unpublishedsuccess>\nLC0019|Extension Lifecycle|Extension failed to un-publish: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#unpublishedfailed>\nLC0020|Extension Lifecycle|Extension compiled successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#compiledsuccess>\nLC0021|Extension Lifecycle|Extension failed to compile: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#compiledfailed>\nLC0022|Extension Lifecycle|Extension updated successfully: {extensionName} version {extensionVersion} by {extensionPublisher}<telemetry-extension-lifecycle-trace#updatedsuccess>\nLC0023|Extension Lifecycle|Extension failed to update: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#updatedfailed>\nLC0024|Table Index Lifecycle|telemetry-table-index-trace#enabled\nLC0025|Table Index Lifecycle|telemetry-table-index-trace#disabled\nLC0026|Extension Lifecycle|Dependent Extension installed successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#dependentinstalledsuccess>\nLC0027|Extension Lifecycle|Dependent extension un-installed successfully: {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-extension-lifecycle-trace#dependentunistalled>\nLC0028|Marketplace Submission|Marketplace submission validation request started: {validationRequestId}<telemetry-appsource-submission-validation-trace#validationrequeststarted>\nLC0029|Marketplace Submission|Marketplace submission validation request completed successfully: {validationRequestId}<telemetry-appsource-submission-validation-trace#validationrequestcompleted>\nLC0030|Marketplace Submission|(Version, country-region) validation started: version {version}, country/region {countryRegion}<telemetry-appsource-submission-validation-trace#versioncountrystarted>\nLC0031|Marketplace Submission|(Version, country-region) validation completed successfully: version {version}, country/region {countryRegion}<telemetry-appsource-submission-validation-trace#versioncountrycompleted>\nLC0032|Marketplace Submission|Extension validation started: version {version}, country/region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-appsource-submission-validation-trace#extensionvalidationstarted>\nLC0033|Marketplace Submission|Extension validation completed successfully: version {version}, country/region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-appsource-submission-validation-trace#extensionvalidationcompleted>\nLC0034|Marketplace Submission|Validation diagnostic reported: version {version}, country/region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-appsource-submission-validation-trace#validationdiagnosticreported>\nLC0035|Marketplace Submission|Marketplace submission validation request completed with failures: {validationRequestId}<telemetry-appsource-submission-validation-trace#submissionrequestcompletedwithfailures>\nLC0036|Marketplace Submission|(Version, country-region) validation completed with failures: version {version}, country-region {countryRegion}<telemetry-appsource-submission-validation-trace#versioncountryvalidationcompletedwithfailures>\nLC0037|Marketplace Submission|Extension validation completed with failures: version {version}, country-region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-appsource-submission-validation-trace#extensionvalidationcompletedwithfailures>\nLC0038|Marketplace Submission|Diagnostic reported on Marketplace submission validation request: {validationRequestId}<telemetry-appsource-submission-validation-trace#submissionrequestdiagnostic>\nLC0040|Task Scheduler|Task {taskId} created: {codeunitObjectId} scheduled to run after {notBefore}. Ready to run: {isReady}<telemetry-task-scheduler-trace#task-created>\nLC0041|Task Scheduler|Task {taskId} ready: {codeunitObjectId} set ready to run after {notBefore}.<telemetry-task-scheduler-trace#task-ready>\nLC0042|Task Scheduler|Task {taskId} removed: {codeunitObjectId}.<telemetry-task-scheduler-trace#task-removed>\nLC0043|Task Scheduler|Task {taskId} main/failure codeunit {codeunitObjectId} completed.<telemetry-task-scheduler-trace#task-completed>\nLC0044|Task Scheduler|Task {taskId} main/failure codeunit {codeunitObjectId} canceled.<telemetry-task-scheduler-trace#task-canceled>\nLC0045|Task Scheduler|Task {taskId} main/failure codeunit {codeunitObjectId} failed.<telemetry-task-scheduler-trace#task-failed>\nLC0057|Task Scheduler|telemetry-task-scheduler-trace#task-timeout-changed-because-it-was-exceeding-the-max-timeout-value\nLC0046|Profile Configuration Lifecycle|Profile import succeeded: {ProfileId} in app/extension {ProfileAppId}<telemetry-profile-configuration-lifecycle-trace#import-success>\nLC0047|Profile Configuration Lifecycle|Profile import failed: {ProfileId} in app/extension {ProfileAppId}<telemetry-profile-configuration-lifecycle-trace#import-failed>\nLC0048|Profile Configuration Lifecycle|telemetry-profile-configuration-lifecycle-trace#export-success\nLC0049|Profile Configuration Lifecycle|Profiles failed to be exported<telemetry-profile-configuration-lifecycle-trace#export-failed>\nLC0050|Profile Configuration Lifecycle|Profile copy succeeded: {ProfileId} to {NewProfileId} from app/extension {ProfileAppId} to app/extension {NewProfileAppId}<telemetry-profile-configuration-lifecycle-trace#copy-success>\nLC0051|Profile Configuration Lifecycle|Profile copy failed: {ProfileId} to {NewProfileId} from app/extension {ProfileAppId} to app/extension {NewProfileAppId}<telemetry-profile-configuration-lifecycle-trace#copy-failed>\nLC0052|Profile Configuration Lifecycle|Profile created successfully: {ProfileId} in app/extension {ProfileAppId}<telemetry-profile-configuration-lifecycle-trace#create-success>\nLC0053|Profile Configuration Lifecycle|Profile removed: {ProfileId} in app/extension {ProfileAppId}<telemetry-profile-configuration-lifecycle-trace#removed>\nLC0054|Profile Configuration Lifecycle|Profile page customization removed: {ProfileId} in app/extension {ProfileAppId}<telemetry-profile-configuration-lifecycle-trace#customization-removed>\nLC0055|Profile Configuration Lifecycle|Profile page customization converted: {ProfileId} in app/extension {ProfileAppId}<telemetry-profile-configuration-lifecycle-trace#customization-converted>\nLC0056|Extension Lifecycle|Extension is already synchronized: {extensionName}<telemetry-extension-lifecycle-trace#alreadySynced>\nLC0058|Permissions|Permission set changed by an extension<telemetry-permission-changes-trace#permissionsetchangedbyapp>\nLC0059|Metadata Embeddings|Metadata embedding generation succeeded for extension {extensionId} version {extensionVersion}<telemetry-metadata-embeddings-trace#LC0059>\nLC0060|Metadata Embeddings|Metadata embedding generation failed for extension {extensionId} version {extensionVersion}<telemetry-metadata-embeddings-trace#LC0060>\nLC0061|Metadata Embeddings|Metadata embedding generation scheduled for extension {extensionId} version {extensionVersion}<telemetry-metadata-embeddings-trace#LC0061>\nLC0062|Metadata Embeddings|Metadata embedding generation started for extension {extensionId} version {extensionVersion}<telemetry-metadata-embeddings-trace#LC0062>\nLC0063|Table Index Lifecycle|Index enabled at runtime: {keyName}<telemetry-table-index-trace#LC0063>\nLC0064|Table Index Lifecycle|Index disabled at runtime: {keyName}<telemetry-table-index-trace#LC0064>\nLC0065|Database schema|Column count exceeded recommended limit for {alObjectType} '{alObjectName}'<telemetry-table-index-trace#LC0065>\nLC0066|Agent Lifecycle|Agent configuration changed: {agentDisplayName}<telemetry-agent-lifecycle-trace#lc0066>\nLC0067|Agent Lifecycle|Agent created: {agentDisplayName}<telemetry-agent-lifecycle-trace#lc0067>\nLC0068|Agent Lifecycle|Agent task created: {taskId}<telemetry-agent-lifecycle-trace#lc0068>\nLC0100|Environment|Environment update available for scheduling: {environmentName} to version {destinationVersion}.<telemetry-environment-lifecycle-trace#environment-update-available>\nLC0101|Environment|Environment update scheduled: {environmentName} to version {destinationVersion}, update on or after date: {registeredForUpdateOnOrAfterDateUtc}<telemetry-environment-lifecycle-trace#environment-update-scheduled>\nLC0102|Environment|Environment update missed: {environmentName} to version {destinationVersion}<telemetry-environment-lifecycle-trace#environment-update-missed>\nLC0103|Environment|Environment update postponed: {environmentName} to version {destinationVersion}<telemetry-environment-lifecycle-trace#environment-update-postponed>\nLC0104|Environment|Environment update resumed: {environmentName} to version {destinationVersion}<telemetry-environment-lifecycle-trace#environment-update-postponed>\nLC0105|Environment|Environment update started: {environmentName} to version {destinationVersion}<telemetry-environment-lifecycle-trace#environment-update-started>\nLC0106|Environment|Environment updated successfully: {environmentName} to version {destinationVersion}<telemetry-environment-lifecycle-trace#environment-updated-successfully>\nLC0107|Environment|Environment failed to update: {environmentName} to version {destinationVersion}<telemetry-environment-lifecycle-trace#environment-failed-to-update>\nLC0110|Environment|telemetry-environment-lifecycle-trace#environment-restart-operation-initiated\nLC0111|Environment|telemetry-environment-lifecycle-trace#environment-restarted-successfully\nLC0112|Environment|telemetry-environment-lifecycle-trace#environment-restart-operation-failed\nLC0113|Environment|telemetry-environment-lifecycle-trace#environment-start-operation-initiated\nLC0114|Environment|telemetry-environment-lifecycle-trace#environment-started-successfully\nLC0115|Environment|telemetry-environment-lifecycle-trace#environment-start-operation-failed\nLC0116|Environment|telemetry-environment-lifecycle-trace#environment-stop-operation-initiated\nLC0117|Environment|telemetry-environment-lifecycle-trace#environment-stopped-successfully\nLC0118|Environment|telemetry-environment-lifecycle-trace#environment-stop-operation-failed\nLC0119|Environment|Environment copy operation started on source: {environmentName} to {destinationEnvironmentName}<telemetry-environment-lifecycle-trace#environment-copy-operation-started-on-source>\nLC0120|Environment|Environment copied successfully: {environmentName} to {destinationEnvironmentName}<telemetry-environment-lifecycle-trace#environment-copied-successfully>\nLC0121|Environment|Environment copy operation failed on source: {environmentName} to {destinationEnvironmentName}<telemetry-environment-lifecycle-trace#environment-copy-operation-failed-on-source>\nLC0122|Environment|Environment copy operation started on destination: {environmentName} from {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-copy-operation-started-on-destination>\nLC0123|Environment|Environment copied successfully to destination: {environmentName} from {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-copied-successfully-to-destination>\nLC0124|Environment|Environment copy operation failed on destination: {environmentName} from {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-copy-operation-failed-on-destination>\nLC0125|Environment|Environment point-in-time restore operation started on source: {environmentName} to {destinationEnvironmentName}<telemetry-environment-lifecycle-trace#environment-point-in-time-restore-operation-started-on-source>\nLC0126|Environment|Environment point-in-time restored successfully: {environmentName} to {destinationEnvironmentName}<telemetry-environment-lifecycle-trace#environment-point-in-time-restored-successfully>\nLC0127|Environment|Environment point-in-time restore operation failed on source: {environmentName} to {destinationEnvironmentName}<telemetry-environment-lifecycle-trace#environment-point-in-time-restore-operation-failed-on-source>\nLC0128|Environment|Environment point-in-time restore operation started on destination: {environmentName} from {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-point-in-time-restore-operation-started-on-destination>\nLC0129|Environment|Environment point-in-time restored successfully to destination: {environmentName} from {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-point-in-time-restored-successfully-to-destination>\nLC0130|Environment|Environment point-in-time restore operation failed on destination: {environmentName} from {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-point-in-time-restore-operation-failed-on-destination>\nLC0131|Environment|Environment move to {destinationAadTenantId} AAD tenant operation scheduled to run at {registeredForMoveDateUtc}: {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-transfer-to-different-entra-tenant-operation-scheduled>\nLC0132|Environment|Environment move to {destinationAadTenantId} AAD tenant operation scheduling failed: {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-transfer-to-different-entra-tenant-operation-scheduling-failed>\nLC0133|Environment|Environment move to {destinationAadTenantId} AAD tenant operation started: {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-transfer-to-different-entra-tenant-operation-started>\nLC0134|Environment|Environment moved to {destinationAadTenantId} AAD tenant successfully: {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-transferred-successfully-to-different-entra-tenant>\nLC0135|Environment|Environment move to {destinationAadTenantId} AAD tenant operation failed: {sourceEnvironmentName}<telemetry-environment-lifecycle-trace#environment-transfer-to-different-entra-tenant-failed>\nLC0136|Environment|telemetry-environment-lifecycle-trace#environment-session-cancellation-started\nLC0137|Environment|telemetry-environment-lifecycle-trace#environment-session-cancelled-successfully\nLC0138|Environment|telemetry-environment-lifecycle-trace#environment-session-cancellation-failed\nLC0139|Environment|telemetry-environment-lifecycle-trace#environment-database-export-operation-started\nLC0140|Environment|telemetry-environment-lifecycle-trace#environment-session-cancelled-successfully\nLC0141|Environment|telemetry-environment-lifecycle-trace#environment-session-cancellation-failed\nLC0142|Environment|Environment configuration key {environmentConfigurationKey} updated for environment {environmentName} to value: {newValue}<telemetry-environment-lifecycle-trace#environment-configuration-key-updated>\nLC0143|Environment|telemetry-environment-lifecycle-trace#environment-configuration-key-failed-to-update\nLC0144|Environment|telemetry-environment-lifecycle-trace#environment-configuration-key-deleted\nLC0145|Environment|telemetry-environment-lifecycle-trace#environment-configuration-key-failed-to-be-deleted\nLC0146|Environment|Environment update window was modified for environment: {environmentName}<telemetry-environment-lifecycle-trace#environment-update-window-modified>\nLC0147|Environment|telemetry-environment-lifecycle-trace#environment-update-window-modification-failed\nLC0149|Environment|telemetry-environment-lifecycle-trace#environment-hard-delete-operation-started\nLC0150|Environment|Environment deleted successfully: {environmentName}<telemetry-environment-lifecycle-trace#environment-hard-deleted>\nLC0151|Environment|telemetry-environment-lifecycle-trace#environment-hard-delete-operation-failed\nLC0152|Environment|telemetry-environment-lifecycle-trace#environment-rename-operation-started\nLC0153|Environment|Environment renamed successfully: {environmentName}<telemetry-environment-lifecycle-trace#environment-renamed>\nLC0154|Environment|telemetry-environment-lifecycle-trace#environment-rename-operation-failed\nLC0155|Environment|Environment app '{extensionName}' hotfix to version {extensionDestinationVersion} scheduled for environment: {environmentName}<telemetry-environment-lifecycle-trace#environment-app-hotfix-scheduled-by-app-management-api>\nLC0156|Environment|Environment app '{extensionName}' hotfix to version {extensionDestinationVersion} scheduling failed for environment: {environmentName}<telemetry-environment-lifecycle-trace#environment-app-hotfix-scheduling-by-app-management-api-failed-to-be-scheduled>\nLC0157|Environment|Environment app '{extensionName}' hotfix to version {extensionDestinationVersion} was cancelled for environment: {environmentName}<telemetry-environment-lifecycle-trace#environment-app-hotfix-cancelled-by-app-management-api>\nLC0158|Environment|Environment app '{extensionName}' hotfix to version {extensionDestinationVersion} started for environment: {environmentName}<telemetry-environment-lifecycle-trace#environment-app-hotfix-started-by-app-management-api>\nLC0159|Environment|Environment app '{extensionName}' hotfix to version {extensionDestinationVersion} applied successfully for environment: {environmentName}<telemetry-environment-lifecycle-trace#environment-app-hotfix-applied-successfully-by-app-management-api>\nLC0160|Environment|Environment app '{extensionName}' hotfix to version {extensionDestinationVersion} failed for environment: {environmentName}<telemetry-environment-lifecycle-trace#environment-app-hotfix-operation-by-app-management-api-failed-to-be-installed>\nLC0161|Extension Lifecycle|Environment app {extensionName} install to version {extensionDestinationVersion} scheduled for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-install-scheduled>\nLC0162|Extension Lifecycle|Environment app {extensionId}, version {extensionDestinationVersion} installation scheduling failed for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-install-schedule-failed>\nLC0163|Extension Lifecycle|Environment app {extensionId}, version {extensionDestinationVersion} installation started for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-install-latest>\nLC0164|Extension Lifecycle|Environment app {extensionName}, version {extensionVersion} installation succeeded for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-install-latest-succeeded>\nLC0165|Extension Lifecycle|Environment app {extensionName}, version {extensionDestinationVersion} installation failed for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-install-failed>\nLC0166|Extension Lifecycle|Environment app {extensionName}, version {extensionDestinationVersion} installation/update requires automatically installing a new dependency app dependencyExtensionName}, version {dependencyExtensionDestinationVersion} for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-dependency-app>\nLC0167|Extension Lifecycle|Environment app {extensionName} update to version {extensionDestinationVersion} scheduled for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-update-scheduled>\nLC0168|Extension Lifecycle|Environment app {extensionId} update to version {extensionDestinationVersion} scheduling failed for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-update-schedule-failed>\nLC0169|Extension Lifecycle|Environment app {extensionId} update to version {extensionDestinationVersion} started for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-update-latest-started>\nLC0170|Extension Lifecycle|Environment app {extensionId} update to version {extensionDestinationVersion} succeeded for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-update-latest-succeeded>\nLC0171|Extension Lifecycle|Environment app {extensionId} update to version {extensionDestinationVersion} failed for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-update-latest-failed>\nLC0173|Extension Lifecycle|Environment app {extensionName} uninstall scheduled for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-uninstall-scheduled>\nLC0174|Extension Lifecycle|Environment app {extensionId} uninstall scheduling failed for environment: {environmentName}<telemetry-extension-lifecycle-trace#app-uninstall-schedule-failed>\nLC0175|Cloud migration|telemetry-cloud-migration-trace#environment-data-upgrade-operation-started\nLC0176|Cloud migration|telemetry-cloud-migration-trace#environment-data-upgrade-operation-completed-successfully\nLC0177|Cloud migration|telemetry-cloud-migration-trace#environment-data-upgrade-operation-failed\nLC0178|Cloud migration|Recovery from a failed data upgrade operation has completed successfully: {environmentName}<telemetry-cloud-migration-trace#recovery-from-a-failed-data-upgrade-operation-has-completed-successfully>\nLC0179|Cloud migration|Recovery from a failed data upgrade operation has failed: {environmentName}<telemetry-cloud-migration-trace#recovery-from-a-failed-data-upgrade-operation-has-failed>\nLC0180|Environment|telemetry-environment-lifecycle-trace#environment-soft-delete-operation-started\nLC0181|Environment|Environment soft deleted successfully: {environmentName}<telemetry-environment-lifecycle-trace#environment-soft-deleted>\nLC0182|Environment|telemetry-environment-lifecycle-trace#environment-soft-delete-operation-failed\nLC0183|Environment|telemetry-environment-lifecycle-trace#environment-recovery-un-delete-operation-started\nLC0184|Environment|Environment recovered successfully: {environmentName}<telemetry-environment-lifecycle-trace#environment-recovered>\nLC0185|Environment|telemetry-environment-lifecycle-trace#environment-recovery-un-delete-operation-failed\nLC0200|Per-tenant extension|PTE validation started: request {submissionId}<telemetry-pte-upload-validation-trace#pte-validation-started>\nLC0201|Per-tenant extension|Diagnostic reported on PTE submission validation request: {submissionId}<telemetry-pte-upload-validation-trace#pte-submission-diagnostic-reported>\nLC0202|Per-tenant extension|PTE submission validation request completed successfully: request {submission id}<telemetry-pte-upload-validation-trace#pte-validation-completed-successfully>\nLC0203|Per-tenant extension|PTE validation completed with failures: request {submissionId}<telemetry-pte-upload-validation-trace#pte-validation-completed-with-failures>\nLC0204|Per-tenant extension|Extension validation started: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-pte-upload-validation-trace#extension-validation-started>\nLC0205|Per-tenant extension|Extension validation completed successfully: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-pte-upload-validation-trace#extension-validation-completed-successfully>\nLC0206|Per-tenant extension|Extension validation completed with failures: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-pte-upload-validation-trace#extension-validation-completed-with-failures>\nLC0207|Per-tenant extension|Dependent extension validation started: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-pte-upload-validation-trace#dependent-extension-validation-started>\nLC0208|Per-tenant extension|Dependent extension validation completed successfully: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-pte-upload-validation-trace#dependent-extension-validation-completed-successfully>\nLC0209|Per-tenant extension|Dependent extension validation completed with failures: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-pte-upload-validation-trace#dependent-extension-validation-completed-with-failures>\nLC0210|Per-tenant extension|Validation diagnostic reported: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-pte-upload-validation-trace#extension-validation-reported>\nLC0220|Environment validation|Environment validation started: environment {environmentName} target build version {targetVersion}<telemetry-environment-validation-trace#environment-validation-started>\nLC0221|Environment validation|Diagnostic reported on validation of environment {environmentId} for target build version {targetVersion}<telemetry-environment-validation-trace#environment-validation-diagnostic-reported>\nLC0224|Environment validation|Extension validation started: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-environment-validation-trace#extension-validation-started>\nLC0225|Environment validation|Extension validation completed successfully: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-environment-validation-trace#extension-validation-completed-successfully>\nLC0226|Environment validation|Extension validation completed with failures: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-environment-validation-trace#extension-validation-completed-with-failures>\nLC0222|Environment validation|Environment validation request completed successfully for {environmentName} target build version {targetVersion}<telemetry-environment-validation-trace#environment-validation-request-completed-successfully>\nLC0223|Environment validation|Environment validation request completed with failures for environment {environmentName} target build version {targetVersion}<telemetry-environment-validation-trace#environment-validation-request-completed-with-failures>\nLC0227|Environment validation|Validation diagnostic reported: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-environment-validation-trace#environment-diagnostic-reported>\nLC0230|Marketplace app breaking changes validation|Marketplace app breaking changes validation started: extension {extensionInfo} for countries/regions {countryCodeList}, and target build version {targetVersion}<telemetry-appsource-app-validation-trace#marketplaceappvalidationstarted>\nLC0231|Marketplace app breaking changes validation|Diagnostic reported on validation of extension {extensionInfo} and target build version {targetVersion}<telemetry-appsource-app-validation-trace#marketplaceappvalidationdiagnosticreported>\nLC0232|Marketplace app breaking changes validation|Marketplace app breaking changes validation completed successfully: extension {extensionInfo}, country {countryCodeList}, and target build version {targetVersion}<telemetry-appsource-app-validation-trace#marketplaceappvalidationcompleted>\nLC0233|Marketplace app breaking changes validation|Marketplace app breaking changes validation completed with failures: extension {extensionInfo} and target build version {targetVersion}<telemetry-appsource-app-validation-trace#marketplaceappvalidationcompletedwithfailure>\nLC0234|Marketplace app breaking changes validation|Extension validation started: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-appsource-app-validation-trace#extensionvalidationstarted>\nLC0235|Marketplace app breaking changes validation|Extension validation completed successfully: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-appsource-app-validation-trace#extensionvalidationcompleted>\nLC0236|Marketplace app breaking changes validation|Validation diagnostic reported: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId}) for country {countryRegion}<telemetry-appsource-app-validation-trace#diagnosticreported>\nLC0237|Marketplace app breaking changes validation|Extension validation completed with failures: extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})<telemetry-appsource-app-validation-trace#extensionvalidationcompletedwithfailures>\n## Runtime events\nEvent ID|Area|Message\nRT0001|Authorization|Authorization Failed (Pre Open Company): {failure reason}<telemetry-authorization-trace#authorizationfailedpreopencompany>\nRT0002|Authorization|Authorization Failed (Open Company): {failure reason}<telemetry-authorization-trace#authorization-failed-open-company>\nRT0003|Authorization|Authorization Succeeded (Pre Open Company)<telemetry-authorization-trace#authorizationsucceededpreopencompany>\nRT0004|Authorization|telemetry-authorization-trace#authorization-succeeded-open-company\nRT0005|Performance|Operation exceeded time threshold (SQL query)<telemetry-long-running-sql-query-trace>\nRT0006|Report generation|telemetry-reports-trace#successful-report-generation\nRT0006|Report generation|Report rendering failed: {report ID} - {report name}<telemetry-reports-trace#failed-report-generation>\nRT0007|Report generation|telemetry-reports-trace#cancellation-report-generation\nRT0008|Incoming Web service requests|Web service called ({category of request}): {endpoint}<telemetry-webservices-trace>\nRT0009|Performance|Executed a SQL statement<telemetry-sql-query-trace#RT0009>\nRT0010|Extension lifecycle|Extension Update Failed: exception raised in extension {extensionName} by {extensionPublisher} (updating to version {extensionTargetedVersion})<telemetry-extension-update-trace#extension-update-failed-exception-raised-in-extension>\nRT0011|Report generation|Report cancelled but a commit occurred<telemetry-reports-trace#commit>\nRT0012|Performance|telemetry-database-locks-trace#database-lock-timed-out\nRT0013|Performance|telemetry-database-locks-trace#database-lock-snapshot-entry\nRT0014|Security|App Key Vault initialization succeeded: '{keyVaultUri}'<telemetry-extension-key-vault-trace#initializedsuccess>\nRT0015|Security|App Key Vault initialization failed<telemetry-extension-key-vault-trace#initializedfailed>\nRT0016|Security|App Key Vault secret retrieval succeeded from key vault '{keyVaultUri}'<telemetry-extension-key-vault-trace#retrievedsuccess>\nRT0017|Security|App Key Vault secret retrieval failed from key vault: '{keyVaultUri}'<telemetry-extension-key-vault-trace#retrievedfailed>\nRT0018|Performance|Operation exceeded time threshold (AL method)<telemetry-al-method-trace>\nRT0019|Outgoing Web service requests|Web Service Called (Outgoing): {endpoint}<telemetry-webservices-outgoing-trace>\nRT0020|Web service key request|Authentication with Web Service Key succeeded: {endpoint}<telemetry-webservices-access-key-trace#succeeded>\nRT0021|Web service key request|Authentication with Web Service Key failed: {endpoint}<telemetry-webservices-access-key-trace#failed>\nRT0022|Security|App secret initialization failed<telemetry-app-resource-exposure-trace#RT0022>\nRT0023|Troubleshooting|Verbose telemetry enabled for session: {sessionId}<telemetry-verbose-logging-trace#enabled>\nRT0024|Troubleshooting|Verbose telemetry disabled for session: {sessionId}<telemetry-verbose-logging-trace#disabled>\nRT0025|Performance|Database wait statistics snapshot taken: {snapshotId}<telemetry-database-wait-statistics-trace#waitstatstaken>\nRT0026|Performance|Database wait statistics snapshot entry: {databaseWaitStatisticsCategory}<telemetry-database-wait-statistics-trace#waitstatsentry>\nRT0027|Performance|Database locks snapshot taken: {snapshotId}<telemetry-database-locks-trace#RT0027>\nRT0028|Performance|telemetry-database-deadlocks-trace#database-deadlock-occurred\nRT0029|Sessions|The StopSession method was invoked on session {stoppingSessionID}<telemetry-stop-session-trace>\nRT0030|Error method call|Error dialog shown: {failureReason}<telemetry-error-method-trace>\nRT0031|Permission error|Permission error shown<telemetry-permission-error-trace>\nRT0032|Permission error|Dependency cycle discovered in permission sets.<telemetry-permission-dependency-cycle-trace>\nRT0033|Web service publishing|Web service metadata error: Name for subpage of parent page '{parentPageName}' is missing. Subpage is skipped.<telemetry-webservices-publish-failure-trace#rt0033>\nRT0034|Web service publishing|Web service metadata error: Control element with id {metadataObjectName} has a missing name. The page with the control was skipped.<telemetry-webservices-publish-failure-trace#rt0034>\nRT0035|Web service publishing|Web service metadata error: The record with name '{webserviceRecordName}' was skipped.<telemetry-webservices-publish-failure-trace#rt0035>\nRT0036|Web service publishing|Web service metadata error: Table field name error, the page contaning the field with caption '{metafieldCaption}' was skipped.<telemetry-webservices-publish-failure-trace#rt0036>\nRT0037|Web service publishing|Web service metadata invalid page<telemetry-api-metadata-validation-trace#RT0037>\nRT0038|Web service publishing|Web service metadata warning: Multiple options while generation navigation property for tablerelation.<telemetry-webservices-publish-failure-trace#rt0038>\nRT0039|Web service publishing|Web service metadata error: The record with name '{entityName}' was skipped.<telemetry-webservices-publish-failure-trace#rt0039>\nRT0040|Business events|Business event subscription created<telemetry-business-events-trace#RT0040>\nRT0041|Business events|Business event subscription deleted<telemetry-business-events-trace#RT0041>\nRT0042|Business events|Business event subscription modified<telemetry-business-events-trace#RT0042>\nRT0043|Business events|Business event subscription enabled<telemetry-business-events-trace#RT0043>\nRT0044|Business events|Business event subscription disabled<telemetry-business-events-trace#RT0044>\nRT0045|Business events|Business event triggered successfully<telemetry-business-events-trace#RT0045>\nRT0046|Business events|Business event trigger failed<telemetry-business-events-trace#RT0046>\nRT0047|Business events|Business event notification sending failed<telemetry-business-events-trace#RT0047>\nRT0048|Web service publishing|Web service conflicting API path<telemetry-api-metadata-validation-trace#RT0048>\nRT00049|Web service publishing|Web service metadata circular API pages<telemetry-api-metadata-validation-trace#RT00049>\nRT0050|Web service publishing|Web service metadata invalid root entity<telemetry-api-metadata-validation-trace#RT0050>\nRT0051|Web service publishing|Web service metadata conflicting navigation property<telemetry-api-metadata-validation-trace#RT0051>\nRT0052|Outgoing Web service requests|HTTP server certificate validation failed when calling endpoint: {endpoint}<telemetry-webservices-outgoing-certificate-validation-errors>\nRT0053|Incoming Web service requests|telemetry-webservices-trace#deprecated-endpoint-called-endpoint\nRT0054|MCP Server|MCP Server tool called: '{toolName}'<telemetry-mcp-server-trace#rt0054>\nRT0055|AI Consumption|AI consumption recorded<telemetry-ai-consumption>\nRT0056|Open in Excel|Open in Excel: {pageName}<telemetry-open-in-excel-trace#RT0056>\n## Find AL event IDs in the application source\nAL application code emits event IDs that start with AL. The application source passes an ID without the AL prefix to Session.LogMessage, the Telemetry codeunit, or the Feature Telemetry codeunit. Business Central adds the AL prefix when it emits the event to Application Insights.\nFor example, the application source emits the configuration package apply event with this pattern:\n```al\nDimensions.Add('PackageCode', ConfigPackage.SystemId);\nSession.LogMessage(\n    '0000E3N',\n    Message,\n    Verbosity::Normal,\n    DataClassification::SystemMetadata,\n    TelemetryScope::All,\n    Dimensions);\n```\nThe resulting event has these values in Application Insights:\n eventId is AL0000E3N.\n The PackageCode dimension is named alPackageCode.\n `TelemetryScope::All` sends the event to the Application Insights resources configured for the environment and the extension publisher.\nTo find the source of an AL event in the Business Central applications repository<https://github.com/microsoft/BCApps>, remove the AL prefix and search for the remaining ID. For example, search for `0000E3N` to find the source of AL0000E3N.\n> NOTE\n> The sections on this page group events by their administrative purpose. An AL event can therefore appear in the Lifecycle events section.\n## Related information\nMonitoring and Analyzing Telemetry<telemetry-overview>\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>\nCreating custom telemetry events for Azure Application Insights<../developer/devenv-instrument-application-for-telemetry-app-insights>"}