{"title":"Analyzing Marketplace submission validation telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-appsource-submission-validation-trace/","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-appsource-submission-validation-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-appsource-submission-validation-trace","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":"Analyze Business Central Marketplace submission validation telemetry to track validation stages, identify diagnostics, and investigate publication failures.","date":"2026-11-17","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Analyzing Marketplace submission validation telemetry","slug":"analyzing-marketplace-submission-validation-telemetry","at":0,"chars":21323},{"level":2,"title":"Validation process overview","slug":"validation-process-overview","at":1141,"chars":1756},{"level":2,"title":"Marketplace submission validation request started","slug":"marketplace-submission-validation-request-started","at":2897,"chars":1478},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":3189,"chars":135},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":3324,"chars":1051},{"level":2,"title":"Diagnostic reported on Marketplace submission validation request","slug":"diagnostic-reported-on-marketplace-submission-validation-request","at":4375,"chars":1751},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":4889,"chars":210},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":5099,"chars":412},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code","at":5511,"chars":615},{"level":2,"title":"(Version, country-region) validation started","slug":"version-country-region-validation-started","at":6126,"chars":1410},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":6256,"chars":174},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":6430,"chars":1106},{"level":2,"title":"Extension validation started","slug":"extension-validation-started","at":7536,"chars":1252},{"level":3,"title":"General dimensions","slug":"general-dimensions-3","at":7651,"chars":255},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-3","at":7906,"chars":882},{"level":2,"title":"Validation diagnostic reported","slug":"validation-diagnostic-reported","at":8788,"chars":2639},{"level":3,"title":"General dimensions","slug":"general-dimensions-4","at":8988,"chars":257},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-4","at":9245,"chars":1251},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code-1","at":10496,"chars":931},{"level":2,"title":"Extension validation completed successfully","slug":"extension-validation-completed-successfully","at":11427,"chars":1288},{"level":3,"title":"General dimensions","slug":"general-dimensions-5","at":11583,"chars":270},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-5","at":11853,"chars":862},{"level":2,"title":"Extension validation completed with failures","slug":"extension-validation-completed-with-failures","at":12715,"chars":1989},{"level":3,"title":"General dimensions","slug":"general-dimensions-6","at":12869,"chars":271},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-6","at":13140,"chars":993},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code-2","at":14133,"chars":571},{"level":2,"title":"(Version, country-region) validation completed successfully","slug":"version-country-region-validation-completed-successfully","at":14704,"chars":1531},{"level":3,"title":"General dimensions","slug":"general-dimensions-7","at":14875,"chars":189},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-7","at":15064,"chars":1171},{"level":2,"title":"(Version, country-region) validation completed with failures","slug":"version-country-region-validation-completed-with-failures","at":16235,"chars":2265},{"level":3,"title":"General dimensions","slug":"general-dimensions-8","at":16404,"chars":190},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-8","at":16594,"chars":1233},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code-3","at":17827,"chars":673},{"level":2,"title":"Marketplace submission validation request completed successfully","slug":"marketplace-submission-validation-request-completed-successfully","at":18500,"chars":952},{"level":3,"title":"General dimensions","slug":"general-dimensions-9","at":18659,"chars":166},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-9","at":18825,"chars":627},{"level":2,"title":"Marketplace submission validation request completed with failures","slug":"marketplace-submission-validation-request-completed-with-failures","at":19452,"chars":1561},{"level":3,"title":"General dimensions","slug":"general-dimensions-10","at":19609,"chars":167},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-10","at":19776,"chars":668},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code-4","at":20444,"chars":569},{"level":2,"title":"Related information","slug":"related-information","at":21013,"chars":310}],"text":"# Analyzing Marketplace submission validation telemetry\nAPPLIES TO: Business Central 2021 release wave 1, version 18.4, and later\nWhen you submit an app to Marketplace using Partner Center, it starts an automated validation process. This technical validation process ensures the extensions in the app meet the technical requirements for going live. It goes through many of the same checks described in technical validation<../developer/devenv-checklist-submission>.\nIf an app's set up for it, telemetry traces are emitted to and recorded in Application Insights. The data provides details about the success or failure of different phases of the validation. See Sending extension telemetry to Azure Application Insights<../developer/devenv-application-insights-for-extensions>.\n> NOTE\n> In order to start analyzing your validation results, use this troubleshooting guide Dynamics 365 Business Central Troubleshooting Guide (TSG) - Marketplace Submission Results (SaaS)<https://github.com/microsoft/BCTech/tree/master/samples/AppInsights/TroubleShootingGuides/D365BC%20Troubleshooting%20Guides%20(TSG)/content/AppSource-Submission-TSG.ipynb>.\n## Validation process overview\nThe validation process starts when you publish the app. The validation runs against each extension in the app, for each country/region (market) specified for the offer in Partner Center, and for each Business Central version that the submission targets. See ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated.\nExtensions are validated using the AL compiler and the AppSourceCop code analyzer<../developer/devenv-using-code-analysis-tool>. Traces are emitted at different phases during the process. Each submission is assigned a unique identifier (ID). This ID is included in each trace for a submission, allowing you to query all traces related to the submission. The general flow for the validation process is illustrated below:\n1. Marketplace submission validation request started\n2. Validation diagnostic reported for information, warnings, or errors that occur on the submission\n3. Version (X), country-region (X) validation started\n4. Extension (X) validation started\n5. Validation diagnostic reported for each error that occurs.\n6. Extension (X) validation completed (successfully or with failures)\n7. Repeat 3-5 for each extension in the submission\n8. Version (X), country-region (X) validation completed (successfully or with failures)\n9. Repeat 2-7 for other country-regions for the Business Central release (X)\n10. Repeat 2-8 for other Business Central releases targeted by the submission\n11. Marketplace submission validation request completed (successfully or with failures)\nTo reduce the risk of failing the Marketplace validation process, review the technical validation<../developer/devenv-checklist-submission> checklist before you submit an app.\n## Marketplace submission validation request started\nOccurs when an app is published from Partner Center. See Review and publish a Dynamics 365 offer - Validation and publishing steps<https://learn.microsoft.com/azure/marketplace/dynamics-365-review-publish#validation-and-publishing-steps>.\n### General dimensions\nDimension|Description or value\nmessage|Marketplace submission validation request started: {validationRequestId}\n### Custom dimensions\nDimension|Description or value\neventId|LC0028\ncountryRegions|Lists the localized versions (markets) of the app that will be validated, like US or DK.\nextensions|Specifies information about the extensions that are part of the submission, which will be validated.\nseverity|Information\nversions|Lists the Business Central release versions<../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated> that the app will be validated against, like 19.0 or 18.4\ncontainsHotfix|Specifies whether the submission contains a hotfix of a Marketplace extension.\nCommon custom dimensions\nThe following table explains other custom dimensions that are common to all Marketplace submission validation traces.\nDimension|Description or value\nvalidationRequestId|Specifies the unique identifier assigned to the app submission validation process. All traces for the submission validation will include this ID.\ntelemetrySchemaVersion|Specifies the version of the Business Central telemetry schema.\n## Diagnostic reported on Marketplace submission validation request\nOccurs during the submission validation request to report diagnostics related to the submission itself. For example, it could be that a submission has duplicate apps, or it doesn't target any Business Central release. This signal isn't necessarily an error, but can also be warning or information. This signal differs from other diagnostic signals like LC0034, which are reported during the compilation of one app for one country/region release.\n### General dimensions\nDimension|Description or value\nmessage|Diagnostic reported on Marketplace submission validation request: {validationRequestId}\nseverityLevel|1 for information, 2 for warning, 3 for error\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0038|\n|diagnosticCode|Specifies the diagnostic identifier, like AS0001 or AL0001.|\n|diagnosticMessage|Specifies the diagnostic message.|\n|diagnosticSeverity|Info, Warning, or Error. Matches the severityLevel.|\n|containsHotfix|Specifies whether the submission contains a hotfix of a Marketplace extension.|\n|See common custom dimensions<#other>||\n### Sample KQL code\nThis KQL code can help you get started analyzing request warnings using the LC0038 event:\n```kql\ntraces\n| where timestamp > ago(1d) // adjust as needed\n| where customDimensions.eventId == 'LC0038'\n| project timestamp\n, requestId = customDimensions.validationRequestId\n, diagnosticCode = customDimensions.diagnosticCode\n, diagnosticMessage = customDimensions.diagnosticMessage\n, diagnosticSeverity = customDimensions.diagnosticSeverity\n, containsHotfix = customDimensions.containsHotfix\n, message\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## (Version, country-region) validation started\nOccurs when the validation has started for a specific version and country/region.\n### General dimensions\nDimension|Description or value\nmessage|(Version, country-region) validation started: version {version}, country/region {countryRegion}\nseverityLevel|1\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0030|\n|allExtensions|Specifies information about the extensions that are part of the submission and extensions that the submission extensions depend on. Select the arrow to expand the dimension to see the details about each extension.|\n|baselineExtensions|Specifies the previous versions of the extensions in the app and the extensions they're dependent on. These extensions form the baseline for validation if publishing a newer version of an app that's already published.|\n|extensions|Specifies the extensions that are part of the submission and will be validated. Select the arrow to expand the dimension to see the details about each extension.|\n|severity|Information|\n|version|Specifies the Business Central release versions<../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated> that the app will be validated against, like 19.0 or 18.4.|\n|containsHotfix|Specifies whether the submission contains a hotfix of a Marketplace extension.|\n|See common custom dimensions<#other>||\n## Extension validation started\nOccurs when the validation for a specific extension in the submission has started.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation started: version {version}, country/region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})\nseverityLevel|1\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0032|\n|countryRegion|Specifies the localized version of the app that will be validated.|\n|extensionId|Specifies the ID of the extension in the submission that will be validated.|\n|extensionName|Specifies the name of the extension in the submission that will be validated.|\n|extensionPublisher|Specifies the publisher of the extension in the submission that will be validated.|\n|extensionVersion|Specifies the version of the extension in the submission that will be validated.|\n|severity|Information|\n|version|Specifies the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the extension will be validated against, like 19.0 or 18.4.|\n|hotfixValidation|Specifies whether the extension validated is a hotfix.|\n|See common custom dimensions<#other>||\n## Validation diagnostic reported\nOccurs when an error occurs during the validation of an extension. The errors are reported by the AL compiler or by the ../developer/analyzers/appsourcecop analyzer.\n### General dimensions\nDimension|Description or value\nmessage|Validation diagnostic reported: version {version}, country/region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})\nseverityLevel|3\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0034|\n|countryRegion|Specifies the localized version of the app that was validated.|\n|diagnosticCode|Specifies the diagnostic identifier, like AS0001 or AL0001.|\n|diagnosticMessage|Specifies the diagnostic error message.|\n|diagnosticSeverity|Error|\n|diagnosticSourceLocation|Specifies the location in the source code where the diagnostic was reported. The format used is (Line, Character).|\n|diagnosticSourcePath|Specifies the path to the file where the diagnostic was reported.|\n|extensionId|Specifies the ID of the extension in the submission that will be validated.|\n|extensionName|Specifies the name of the extension in the submission that was validated.|\n|extensionPublisher|Specifies the publisher of the extension in the submission that was validated.|\n|extensionVersion|Specifies the version of the extension in the submission that was validated.|\n|severity|Error|\n|version|Specifies the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the extension was validated against, like 19.0 or 18.4.|\n|hotfixValidation|Specifies whether the extension validated is a hotfix.|\n|See common custom dimensions<#other>||\n### Sample KQL code\nThis KQL code can help you get started analyzing request failures using the LC0034 event:\n```kql\ntraces\n| where timestamp > ago(1d) // adjust as needed\n| where customDimensions.eventId == 'LC0034'\n| project timestamp\n, countryRegion = customDimensions.countryRegion\n, version = customDimensions.version\n, extensionId = customDimensions.extensionId\n, extensionName = customDimensions.extensionName\n, extensionPublisher = customDimensions.extensionPublisher\n, extensionVersion = customDimensions.extensionVersion\n, diagnosticCode = customDimensions.diagnosticCode\n, diagnosticMessage = customDimensions.diagnosticMessage\n, diagnosticSeverity = customDimensions.diagnosticSeverity\n, diagnosticSourceLocation = customDimensions.diagnosticSourceLocation\n, diagnosticSourcePath = customDimensions.diagnosticSourcePath\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## Extension validation completed successfully\nOccurs when the validation for a specific extension in the submission has completed, and no errors occurred.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation completed successfully: version {version}, country/region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})\nseverityLevel|1\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0033|\n|countryRegion|Specifies the localized version of the app that was validated.|\n|extensionId|Specifies the ID of the extension in the submission that will be validated.|\n|extensionName|Specifies the name of the extension in the submission that was validated.|\n|extensionPublisher|Specifies the publisher of the extension in the submission that was validated.|\n|extensionVersion|Specifies the version of the extension in the submission that was validated.|\n|severity|Information|\n|version|Specifies the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the extension was validated against, like 19.0 or 18.4.|\n|hotfixValidation|Specifies whether the extension validated is a hotfix.|\n|See common custom dimensions<#other>||\n## Extension validation completed with failures\nOccurs when the validation for a specific extension in the submission has completed, but errors occurred.\n### General dimensions\nDimension|Description or value\nmessage|Extension validation completed with failures: version {version}, country-region {countryRegion} for extension {extensionName} version {extensionVersion} by {extensionPublisher} ({extensionId})\nseverityLevel|3\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0037|\n|countryRegion|Specifies the localized version of the app that was validated.|\n|extensionId|Specifies the ID of the extension in the submission that will be validated.|\n|extensionName|Specifies the name of the extension in the submission that was validated.|\n|extensionPublisher|Specifies the publisher of the extension in the submission that was validated.|\n|extensionVersion|Specifies the version of the extension in the submission that was validated.|\n|failureReason|One or more error diagnostics were reported. For more information about the diagnostics, see traces with eventId LC0034.|\n|severity|Error|\n|version|Specifies the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the extension was validated against, like 19.0 or 18.4.|\n|hotfixValidation|Specifies whether the extension validated is a hotfix.|\n|See common custom dimensions<#other>||\n### Sample KQL code\nThis KQL code can help you get started analyzing request failures using the LC0037 event:\n```kql\ntraces\n| where timestamp > ago(1d) // adjust as needed\n| where customDimensions.eventId == 'LC0037'\n| project timestamp\n, requestId = customDimensions.validationRequestId\n, countryRegion = customDimensions.countryRegion\n, version = customDimensions.version\n, extensionName = customDimensions.extensionName\n, failureReason = customDimensions.failureReason\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## (Version, country-region) validation completed successfully\nOccurs when the validation has completed for a specific version and country/region, and no errors occurred.\n### General dimensions\nDimension|Description or value\nmessage|(Version, country-region) validation completed successfully: version {version}, country/region {countryRegion}\nseverityLevel|1\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0031|\n|allExtensions|Specifies information about the extensions that were part of the submission and extensions that the submission extensions depend on. Select the arrow to expand the dimension to see the details about each extension.|\n|baselineExtensions|Specifies the previous versions of the extensions in the app and the extensions they're dependent on. These extensions form the baseline for validation if publishing a newer version of an app that's already published.|\n|countryRegion|Specifies the localized version of the app that was validated.|\n|extensions|Specifies the extensions that were part of the submission and were validated. Select the arrow to expand the dimension to see the details about each extension.|\n|severity|Information|\n|version|Specifies the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the app was validated against, like 19.0 or 18.4.|\n|containsHotfix|Specifies whether the (Version, country-region) validation contains a hotfix of a Marketplace extension.|\n|See common custom dimensions<#other>||\n## (Version, country-region) validation completed with failures\nOccurs when the validation has completed for a specific version and country/region, and errors occurred.\n### General dimensions\nDimension|Description or value\nmessage|(Version, country-region) validation completed with failures: version {version}, country-region {countryRegion}\nseverityLevel|3\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0036|\n|allExtensions|Specifies information about the extensions that were part of the submission and extensions that the submission extensions depend on. Select the arrow to expand the dimension to see the details about each extension.|\n|baselineExtensions|Specifies the previous versions of the extensions in the app and the extensions they're dependent on. These extensions form the baseline for validation if publishing a newer version of an app that's already published.|\n|countryRegion|Specifies the localized version of the app that was validated.|\n|extensions|Specifies the extensions that were part of the submission and were validated. Select the arrow to expand the dimension to see the details about each extension.|\n|failureReason|One or more extension validation tasks have failed.|\n|severity|Error|\n|version|Specifies the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the app was validated against, like 19.0 or 18.4.|\n|containsHotfix|Specifies whether the (Version, country-region) validation contains a hotfix of a Marketplace extension.|\n|See common custom dimensions<#other>||\n### Sample KQL code\nThis KQL code can help you get started analyzing request failures using the LC0036 event:\n```kql\ntraces\n| where timestamp > ago(1d) // adjust as needed\n| where customDimensions.eventId == 'LC0036'\n| project timestamp\n, requestId = customDimensions.validationRequestId\n, countryRegion = customDimensions.countryRegion\n, version = customDimensions.version\n, extensions = customDimensions.extensions\n, allExtensions = customDimensions.allExtensions\n, baselineExtensions = customDimensions.baselineExtensions\n, failureReason = customDimensions.failureReason\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## Marketplace submission validation request completed successfully\nOccurs when the submission validation process has fully completed, and no errors occurred.\n### General dimensions\nDimension|Description or value\nmessage|Marketplace submission validation request completed successfully: {validationRequestId}\nseverityLevel|1\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0029|\n|countryRegions|Lists the localized versions (markets) of the app that were validated, like US or DK.|\n|extensions|Specifies information about the extensions that were part of the submission and validated.|\n|severity|Information|\n|versions|Lists the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the app was validated against, like 19.0 or 18.4.|\n|containsHotfix|Specifies whether the submission contains a hotfix of a Marketplace extension.|\n|See common custom dimensions<#other>||\n## Marketplace submission validation request completed with failures\nOccurs when the submission validation process has fully completed, but errors occurred.\n### General dimensions\nDimension|Description or value\nmessage|Marketplace submission validation request completed with failures: {validationRequestId}\nseverityLevel|3\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|LC0035|\n|countryRegions|Lists the localized versions (markets) of the app that were validated, like US or DK.|\n|extensions|Specifies the extensions that were part of the submission and validated.|\n|failureReason|One more extension validation tasks have failed.|\n|severity|Error|\n|versions|Lists the ../developer/devenv-checklist-submission#against-which-releases-of-business-central-is-your-submission-validated that the app was validated against, like 19.0 or 18.4.|\n|containsHotfix|Specifies whether the submission contains a hotfix of a Marketplace extension.|\n|See common custom dimensions<#other>||\n### Sample KQL code\nThis KQL code can help you get started analyzing request failures using the LC0035 event:\n```kql\ntraces\n| where timestamp > ago(1d) // adjust as needed\n| where customDimensions.eventId == 'LC0035'\n| project timestamp\n, requestId = customDimensions.validationRequestId\n, countryRegions = customDimensions.countryRegions\n, versions = customDimensions.versions\n, extensions = customDimensions.extensions\n, failureReason = customDimensions.failureReason\n```\nTo learn more about how to set up alerting on Business Central telemetry, see telemetry-alert.\n## Related information\ntelemetry-overview\nSending App Telemetry to Azure Application Insights<../developer/devenv-application-insights-for-extensions>\ntelemetry-alert\nTechnical Validation Checklist<../developer/devenv-checklist-submission>\nTechnical Validation FAQ<../developer/devenv-checklist-submission-faq>"}