{"title":"Available telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-available-telemetry/","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-available-telemetry, 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-available-telemetry","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":"Find Business Central telemetry by area or event ID to monitor environments and extensions, diagnose errors, and analyze performance.","date":"2026-11-17","meta":{"topic":"overview"},"outline":[{"level":2,"title":"Telemetry by area","slug":"telemetry-by-area","at":104,"chars":10645},{"level":2,"title":"Telemetry by event ID","slug":"telemetry-by-event-id","at":10749,"chars":50428},{"level":3,"title":"Application events","slug":"application-events","at":10895,"chars":4572},{"level":3,"title":"Client events","slug":"client-events","at":15467,"chars":408},{"level":3,"title":"Lifecycle events","slug":"lifecycle-events","at":15875,"chars":38428},{"level":3,"title":"Runtime events","slug":"runtime-events","at":54303,"chars":6874},{"level":2,"title":"Related information","slug":"related-information","at":61177,"chars":130}],"text":"In Application Insights, telemetry from Business Central is logged into the traces or pageViews tables.\n## Telemetry by area\nCurrently, Business Central offers telemetry on the following operations:\nArea|Description|Online|On-premises|Extension support|More information\nAgent Lifecycle #13|Provides information about agent creation, configuration changes, and task creation.|✓|||telemetry-agent-lifecycle-trace\nAI Consumption #11|Provides information about Copilot Credits consumed by features subject to consumption-based billing<tenant-admin-center-manage-consumption-billing>.|✓||✓|telemetry-ai-consumption\nApp key vault secrets|Provides information about the retrieval of secrets from Azure Key Vaults by extensions.|✓#1|✓#1|✓|telemetry-extension-key-vault-trace\nApp resource exposure policy #12|Provides information about failures when parsing resource exposure policy overrides in extensions.|✓|✓||telemetry-app-resource-exposure-trace\nAPI metadata validation #12|Provides information about API page metadata validation errors during API generation.|✓|✓||telemetry-api-metadata-validation-trace\nAuthorization|Provides information about user sign-in attempts. Information includes success or failure indication, reason for failure, user type, and more.|✓|✓||telemetry-authorization-trace\nAzure Function Integration#6|Provides information about requests to Azure Functions from Business Central|✓|✓||telemetry-azure-function-integration-trace\nBusiness events #9|Provides information about business event subscription lifecycle and execution.|✓|✓||telemetry-business-events-trace\nChangelog configuration changes#9|Provides information about changes to the configuration of the change log.|✓|✓||telemetry-changelog-configuration-trace\nClient actions#7|Provides information about usage of client features.|✓|✓||telemetry-client-action-trace\nClient control add-in exception#11|Provides information about operations done on configuration packages, including exporting, importing, applying, and deleting.|✓|✓||telemetry-client-add-in-exceptions\nCloud migration#8|Provides information about cloud migration setup, replication runs, and data upgrade|✓|||telemetry-cloud-migration-trace\nCompany lifecycle|Provides information about creating, copying, and deleting of companies.|✓|✓||telemetry-company-lifecycle-trace\nConfiguration package lifecycle|Provides information about operations done on configuration packages, including exporting, importing, applying, and deleting.|✓|✓||telemetry-configuration-package-trace\nDatabase deadlocks#5|Provides information about database deadlocks that occur.|✓|✓||telemetry-database-deadlocks-trace\nDatabase lock timeouts|Provides information about database locks that timed out.|✓|✓||telemetry-database-locks-trace\nDatabase wait statistics|Provides information about the wait categories and the wait times a query runs into.|✓|✓||telemetry-database-wait-statistics-trace\nEmail|Provides information about the success or failure of sending emails.|✓|✓||telemetry-email-trace\nEnvironment lifecycle #5|Provides information about changes and operations on an environment, like updates, hotfixes, copy, move, delete, configuration changes, and more.|✓|||telemetry-environment-lifecycle-trace\nEnvironment validation #7|Provides information about proactive validations on extensions in the environment against the next release.|✓|||telemetry-environment-validation-trace\nError message quality#5|Provides information about error messages that users thought were helpful or unhelpful.|✓|✓||telemetry-error-message-voting-trace\nError method|Provides information about error dialogs that are shown to the users.|✓|✓|✓|telemetry-error-method-trace\nExtension lifecycle #2|Provides information about the success or failure of extension-related operations, like publishing, synchronizing, installing, and more.|✓|✓|✓|telemetry-extension-lifecycle-trace\nExtension update|Provides information about errors that occur and upgrade tags used when upgrading an extension.|✓|✓|✓|telemetry-extension-update-trace\nExtension Upload Validation#9|Provides information about validations when a user/administrator uploads a per-tenant extension to an environment from the Extension Management page.|✓|||telemetry-pte-upload-validation-trace\nFeature Management#7|Provides information about the state changes done on the Feature Management page.|✓|✓||telemetry-feature-management-trace\nFeature telemetry|Provides information about the usage and errors of features.|✓|✓|Through a registered publisher telemetry logger.|Using feature telemetry<telemetry-feature-telemetry>\nField monitoring trace|Provides information about the usage of the field monitoring feature.|✓|✓||telemetry-field-monitoring-trace\nFinancial report lifecycle#11|Provides data about the lifecycle operations in financial reporting.|✓|✓||telemetry-financial-report-lifecycle-trace\nFinancial report usage#11|Provides data about the usage of the financial reports: Financial report run on-screen and Financial report run from request page.|✓|✓||telemetry-financial-report-usage-trace\nJob queue|Provides information about creating and running job queue entries.|✓|✓||telemetry-job-queue-lifecycle-trace\nLong running AL method trace#3|Provides information about long running AL methods.|✓|✓|✓|telemetry-al-method-trace\nLong running operation (SQL query)|Provides information about SQL queries that take longer than expected to execute.|✓|✓|✓|telemetry-long-running-sql-query-trace\nMCP configuration#13|Provides information about creating, modifying, and deleting MCP (Model Context Protocol) configurations.|✓|✓||telemetry-mcp-configuration-trace\nMCP Server#13|Provides information about tool calls made through MCP Server configurations.|✓|||telemetry-mcp-server-trace\nMarketplace app breaking changes validation|Provides information about ongoing validations checking if an app compiles and meets technical requirements across upcoming Business Central versions.|✓||✓|telemetry-appsource-app-validation-trace\nMarketplace Submission Validation|Provides information about validation when an extension is submitted to Marketplace.|✓||✓|telemetry-appsource-submission-validation-trace\nMetadata embeddings#13|Provides information about embedding generation lifecycle for extensions, used to power AI features like Copilot search.|✓|||telemetry-metadata-embeddings-trace\nOnboarding#7|Provides information about the onboarding of users.|✓|✓||telemetry-onboarding-trace\nOpen in Excel #14|Provides information about when users export data to Excel using the Open in Excel action.|✓|✓||telemetry-open-in-excel-trace\nPage views|Provides information about the pages that users open in the modern client.|✓|✓#6|✓#4|telemetry-page-view-trace\nPerformance Toolkit (BCPT)|Provides information about test results from running the Business Central Performance Toolkit (BCPT).|✓|✓||telemetry-performance-toolkit-trace\nPermissions|Provides information about adding, removing, and assigning permission sets.|✓|||telemetry-permission-changes-trace\nPermissions dependency cycle#5|Provides information about dependency cycles in permissions.|✓|✓||telemetry-permission-dependency-cycle-trace\nPermission error#5|Provides information about errors related to permissions that users get.|✓|✓||telemetry-permission-error-trace\nProfile configuration lifecycle#6|Provides information about design operations done on profiles from the client.|✓|✓||telemetry-profile-configuration-lifecycle-trace\nReport generation|Provides information about the execution of reports.|✓|✓|✓|telemetry-reports-trace\nReport layout lifecycle#10|Provides information about actions taken by users on report layouts.|✓|✓|✓|telemetry-reports-trace\nRetention policy trace#3|Provides information about the usage of the retention policy feature.|✓|✓||telemetry-retention-policy-trace\nSQL query trace #12|Provides verbose logging of all SQL queries when additional logging is enabled.|✓|✓||telemetry-sql-query-trace\nStopped sessions#5|Provides information about background sessions that were forcibly stopped from the admin center or by calling the StopSession method from AL.|✓|✓|AL calls with extension context.|telemetry-stop-session-trace\nTable index trace#3|Provides information about the addition or removal of a table index.|✓|✓|✓|telemetry-table-index-trace\nTask scheduler lifecycle|Provides information the execution of scheduled tasks.|✓|✓||telemetry-task-scheduler-trace\nUser checklists#5|Provides information about when the status of a user checklist changes|✓|✓||telemetry-user-checklist-trace\nVerbose logging enabled/disabled#5|Provides information about when additional logging is enabled and disabled from the client.|✓|✓||telemetry-verbose-logging-trace\nWeb service access key authentication|Provides information about the authentication of web server access keys on web service requests.|✓|✓||telemetry-webservices-access-key-trace\nWeb service publish failures#8|Provides information about the web services publish failures.|✓|✓|✓|telemetry-webservices-publish-failure-trace\nWeb service requests (incoming)|Provides information about the execution time of incoming web service requests.|✓|✓|✓|telemetry-webservices-trace\nWeb service requests (outgoing )|Provides information about the execution time of outgoing web service requests.|✓|✓|✓|telemetry-webservices-outgoing-trace\nWeb service requests (outgoing ): Server certificate validation errors#11|Provides information data about errors in validating server certificates on the endpoint when doing outgoing web service requests using the AL HTTPClient module.|✓|✓||telemetry-webservices-outgoing-certificate-validation-errors\n1This signal is only emitted to the Application Insights resource that's specified in the extension.\n2Introduced in Business Central 2020 release wave 1, version 16.3. For extension telemetry, this signal was introduced in 2020 release wave 2, version 17.1.\n3Introduced in Business Central 2020 release wave 2, version 17.1. For extension telemetry, this signal was introduced in 2021 release wave 1, version 18.1.\n4Introduced in Business Central 2021 release wave 1, version 18.\n5Introduced in Business Central 2022 release wave 1, version 20.\n6Introduced in Business Central 2022 release wave 2, version 21.\n7Introduced in Business Central 2023 release wave 1, version 22.\n8Introduced in Business Central 2023 release wave 1, version 22.1.\n9Introduced in Business Central 2023 release wave 2, version 23.\n10Introduced in Business Central 2024 release wave 2, version 25.1.\n11Introduced in Business Central 2025 release wave 1, version 26.0.\n12Introduced in Business Central 2025 release wave 1, version 26.1.\n13Introduced in Business Central 2026 release wave 1, version 28.0.\n14Introduced in Business Central 2026 release wave 2, version 29.0.\n## Telemetry by event ID\nThe following tables list the IDs of Business Central telemetry events that are emitted into 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## Related information\ntelemetry-event-ids\nEnable Sending Telemetry to Application Insights<telemetry-enable-application-insights>"}