Troubleshoot the Veeva Vault connector
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page describes common errors when using the Veeva Vault connector.
Pipeline fails after a full refresh is triggered
Symptom: After triggering a full refresh, the pipeline fails or appears to produce no data on the first run.
Cause: Full refreshes require two pipeline updates to complete. The first update clears the staged archive state from the Unity Catalog staging volume. The second update downloads and processes the new full archive.
Solution: Run the pipeline a second time after the first update completes.
No new data after recent pipeline run
Symptom: The pipeline runs successfully but no new records are ingested.
Cause: Veeva generates incremental archives every 15 minutes. If the pipeline runs more frequently than this, subsequent runs may find no new archives.
Solution: Schedule the pipeline to run no more frequently than every 15 minutes.
Pipeline requires full refresh after extended downtime
Symptom: The pipeline fails with an error indicating that incremental archives are no longer available.
Cause: Veeva retains incremental archives for only 10 days. If the pipeline has not run for more than 10 days, the incremental archive chain is broken.
Solution: Trigger a full refresh of the pipeline. Note that a full refresh spans two pipeline updates. See Full refresh behavior.
Authentication failure when creating a connection
Symptom: The connection fails to authenticate during setup.
Cause: One or more connection parameters are incorrect. Common issues include:
- An expired or invalid Microsoft Entra ID client secret.
- An incorrect Vault Session ID URL from the OAuth 2.0 / OpenID Connect profile.
- The Federated ID on the Veeva service account user does not match the Microsoft Entra ID Client ID.
Solution: Verify each connection parameter against the values obtained during source setup. If the Microsoft Entra ID client secret has expired, generate a new one and update the connection. See Configure Veeva Vault for OAuth 2.0 M2M authentication.