Issues with Enterprise ChatGPT Purview Scanning

Hello **HCM,**Thank you for reporting this issue. We understand that your scans are failing with Error (3819): Unhandled exception caught when processing data after previously working successfully.

We are currently reviewing the information provided to better understand the cause of this behavior. We will update you with our findings and next steps as soon as we have more information.

Thank you for your patience.

Vemula,

Any update on this? We need to get this working as its part of setting up compliance.

HI @HCM ,

Thank you for sharing the details.

The Error (3819): “Unhandled exception caught when processing data, please retry” appears to be occurring during the Microsoft Purview scan of the ChatGPT Enterprise data source. Since the connector was initially working and the scans subsequently started failing, I would recommend validating the connector configuration and prerequisites before recreating the scan.

Please verify the following:

• In Microsoft Purview > Data Map > Sources > ChatGPT Enterprise, open the configured scan and run Test connection to confirm that the connection is still successful.
• Verify that the API key stored in Azure Key Vault is valid and that the Purview credential references the correct secret and secret version.
• Confirm that the API key has the required Compliance API read scope. Microsoft Purview requires at least read access to retrieve ChatGPT Enterprise metadata.
• Verify that pay-as-you-go billing is enabled for the Microsoft Purview organization.
• Confirm that the required Purview permissions and the collection policy for ingesting ChatGPT Enterprise prompts and responses are still configured.
• If the initial/full scan completed successfully, use an incremental scan for subsequent runs rather than creating a new scan.

Microsoft documentation also notes that, because of current API limitations, ChatGPT Enterprise conversations can be ingested approximately 24 hours after they occur, so a delay in newly generated interactions appearing in Purview can be expected.

If Test connection succeeds but the scan continues to fail with Error 3819, this is likely to require investigation of the Purview scan execution/backend logs. In that situation, please raise or reopen the support request under Microsoft Purview / Data Map / Scanning and ingestion rather than a generic Azure resource category.

When opening the case, provide the Purview account/tenant details, ChatGPT Enterprise source name, scan name, Scan ID/Run ID, UTC timestamp of the failed scan, region, and the complete Error 3819 message. These details should allow the support/engineering team to correlate the failed scan with backend logs.

Please avoid deleting and recreating the existing source or scan until the failed run has been investigated, as the existing Scan ID and run history can be useful for troubleshooting.

https://learn.microsoft.com/en-in/purview/archive-chatgpt-interactions?utm_source