> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/connectors/troubleshooting-and-faqs.md).

# Troubleshooting & FAQs

## Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="59.92578125" valign="top">S. No</th><th width="169.578125" valign="top">Error Message</th><th width="428.59375" valign="top">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">Connection validation fails for a SharePoint site using a /teams/ address</td><td valign="top"><p>The current SharePoint connector searches for sites under /sites/. It does not connect to a site whose address uses /teams/.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the site address in SharePoint and identify whether it uses /sites/ or /teams/.</li><li>For a /teams/ site, note that the current connector cannot validate or crawl the site.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">Microsoft Fabric Managed Airflow connection fails with Microsoft Entra ID</td><td valign="top"><p>The Apache Airflow connector supports Basic Authentication with a username and password. Microsoft Entra ID authentication is not currently supported.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the Airflow endpoint uses the native REST API and supports Basic Authentication.</li><li>If the environment requires Microsoft Entra ID, record this as a connector capability gap.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">Connection to an S3 compatible storage endpoint fails</td><td valign="top"><p>The current S3 connector does not support non-AWS S3 endpoints or on-premises S3 compatible deployments.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm that the endpoint is AWS S3 and that the configured region is valid.</li><li>For buckets in different AWS regions, provide the correct region for each bucket.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">Microsoft Fabric Managed Airflow connection is rejected</td><td valign="top"><p>The Apache Airflow connector supports Basic Authentication against the native Airflow REST API. Microsoft Entra ID authentication is not currently supported.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the authentication method required by the Fabric Airflow endpoint.</li><li>If Microsoft Entra ID is mandatory, treat support as an enhancement request for feasibility review.</li></ul></td></tr><tr><td valign="top">5</td><td valign="top">A connection stops working after a server migration</td><td valign="top"><p>OvalEdge connects to source systems using a DNS name or IP address, not a MAC address.</p><p><strong>Resolution</strong>:</p><ul><li>If the configured DNS name remains unchanged, an IP address change alone does not require a connector update.</li><li>If the configured DNS name changes, update the connection details.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Compatibility" %}

<table data-search="true"><thead><tr><th width="59.48046875" valign="top">S. No</th><th width="167.58984375" valign="top">Error Message</th><th width="435.578125" valign="top">Error Descriptionm &#x26; Resolution</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">A connector cannot connect to a compatible database or storage system</td><td valign="top"><p>Protocol compatibility does not guarantee full compatibility. A derived product may differ in query behavior, APIs, endpoints, or deployment requirements.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the exact product name and version.</li><li>Collect the official technical documentation and details of any compatibility layer or custom settings.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">Metadata crawling fails for a SingleStore database</td><td valign="top"><p>SingleStore is MySQL protocol-compatible, but its metadata behavior has not been validated for the OvalEdge MySQL connector.</p><p><strong>Resolution</strong>:</p><ul><li>Record the exact SingleStore version and the metadata operations required.</li><li>Do not assume that MySQL permissions or queries behave identically in SingleStore.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">NetSuite Finance metadata is missing</td><td valign="top"><p>NetSuite Finance use cases are associated with the NetSuite ERP connector, not the NetSuite CRM connector. The ERP connector is in Pilot status with limited coverage and has not been recently validated.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm the required Finance objects and use cases.</li><li>Review the available connector documentation and treat capabilities as subject to validation.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">A Z Drive location cannot be identified for crawling</td><td valign="top"><p>The name Z Drive can refer to different products or storage solutions, so connector compatibility cannot be confirmed from the name alone.</p><p><strong>Resolution</strong>:</p><ul><li>Identify the product name, vendor, access method, and storage technology.</li><li>Provide product documentation or a sample location for assessment.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Lineage" %}

<table data-search="true"><thead><tr><th width="59.10546875" valign="top">S. No</th><th width="169.99609375" valign="top">Error Message</th><th width="430.3046875" valign="top">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">Lineage is missing for YAML files</td><td valign="top"><p>Automatic lineage parsing for YAML files is not available out of the box. A custom approach may be possible after reviewing the file structure and transformation logic.</p><p><strong>Resolution</strong>:</p><ul><li>Collect representative YAML samples and confirm where the files are stored.</li><li>Document the ETL platform name, version, and transformations described in the files.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">Lineage is missing for custom Java code</td><td valign="top"><p>Native automatic lineage extraction from Java code is not currently supported. An AI-based approach may be explored, but complete accuracy is not guaranteed.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm which Java files and transformation steps need lineage.</li><li>Provide representative source code and expected lineage examples for assessment.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">Lineage is not available for a pilot or beta connector</td><td valign="top"><p>Pilot and beta connectors may have limited capabilities and may not have been validated against current product versions or environments.</p><p><strong>Resolution</strong>:</p><ul><li>Review the connector documentation and its stated capability limits.</li><li>Confirm the exact source product and version that must be connected.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">SSAS metadata cannot be crawled from exported files alone</td><td valign="top"><p>The current SSAS connector uses live connectivity for metadata crawling. Model files such as ASDATABASE or XMLA files are used for lineage building, not for file-based metadata crawling. Profiling requires live access to the SSAS model.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm whether live SSAS connectivity is available.</li><li>If only files are available, identify the required metadata and lineage use cases before planning an alternative.</li></ul></td></tr><tr><td valign="top">5</td><td valign="top">Salesforce lineage or data quality results are unavailable</td><td valign="top"><p>The current Salesforce integration does not capture enough object flow information for Auto Lineage. Salesforce data structures and SOQL also limit Data Quality coverage compared with SQL systems.</p><p><strong>Resolution</strong>:</p><ul><li>Use the connector documentation to confirm the supported metadata and profiling operations.</li><li>For lineage, assess whether Apex methods or triggers meet the use case; this requires further evaluation.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling and Profiling" %}

<table data-search="true"><thead><tr><th width="59.21484375" valign="top">S. No</th><th width="169.76953125" valign="top">Error Message</th><th width="437.8203125" valign="top">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">Profiling runs for an unexpectedly long time</td><td valign="top"><p>Profiling duration depends on data volume, table size, selected attributes, and the amount of data scanned. Large data volumes can increase processing time and source-system load.</p><p><strong>Resolution</strong>:</p><ul><li>Review the selected profiling attributes and whether full or sample profiling is required.</li><li>Review the profiling schedule and consider smaller batches where supported.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">A large cataloging workload does not meet expected performance</td><td valign="top"><p>Processing capacity depends on the number and type of catalog objects, job scheduling frequency, and workload distribution. Horizontal scaling is not configured automatically for job pods.</p><p><strong>Resolution</strong>:</p><ul><li>Estimate the number of schemas, tables, reports, columns, and other objects by source system.</li><li>Document the expected crawl schedule and frequency.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">A custom reporting application does not appear in the catalog</td><td valign="top"><p>Applications built with a general programming framework do not receive automatic connector support unless the reporting system is supported.</p><p><strong>Resolution</strong>:</p><ul><li>Check whether the reporting product appears in the supported connector documentation.</li><li>Identify available APIs, SDKs, or export files that contain the required metadata.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">SAP ECC metadata cannot be retrieved</td><td valign="top"><p>The SAP Tables integration can retrieve raw table metadata from the underlying SAP ECC database, but the integration is classified as Pilot and may require custom BAPI functions in the SAP environment.</p><p><strong>Resolution</strong>:</p><ul><li>Confirm whether the required BAPI functions already exist or need development.</li><li>Arrange access to an SAP ECC test environment and an SAP subject matter expert for validation.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## FAQs

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="58.921875" valign="top">S. No</th><th width="169.72265625" valign="top">Question</th><th width="431.47265625" valign="top">Answer</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">Does the Apache Airflow connector support Microsoft Entra ID authentication?</td><td valign="top"><ul><li>The current Apache Airflow connector supports Basic Authentication with a username and password against the native Airflow REST API.</li><li>Microsoft Entra ID authentication is not currently supported.</li><li>A managed Airflow service that requires Entra ID is not supported out of the box and requires a feasibility assessment for any enhancement.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">Does OvalEdge support Kerberos authentication?</td><td valign="top"><ul><li>Kerberos authentication is supported for legacy SQL Server environments through the underlying Microsoft JDBC Driver.</li><li>Windows Authentication can use the configured Active Directory and Kerberos infrastructure.</li><li>Support for other source systems depends on the connector and its authentication options.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">What permissions are required for connector setup?</td><td valign="top"><ul><li>Required permissions depend on the source system, authentication method, and connector operations.</li><li>Common prerequisites include valid credentials, read access to required metadata, access to configured paths, and network connectivity.</li><li>Review the specific connector guide for required roles, ports, and permissions before validation.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">Can SharePoint On Premises be connected?</td><td valign="top"><ul><li>The final internal clarification in the supplied table confirms that SharePoint on-premises is supported.</li><li>Confirm the deployment details and authentication requirements against the applicable connector documentation before setup.</li></ul></td></tr><tr><td valign="top">5</td><td valign="top">Will a server IP address change require a new connector?</td><td valign="top"><ul><li>No, not if the connector uses a DNS name that remains unchanged.</li><li>If the configured DNS name changes, update the connection details.</li><li>If the connector uses an IP address and that address changes, update the IP address. The connector does not need to be recreated.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling" %}

<table><thead><tr><th width="58.8359375" valign="top">S. No</th><th width="169.5703125" valign="top">Question</th><th width="431.48046875" valign="top">Answer</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">Can PDF, Word, and text files be previewed?</td><td valign="top"><ul><li>PDF, DOC, DOCX, and TXT preview support is not confirmed as a general capability in the source assessment.</li><li>The reviewed response explicitly states that DOC, DOCX, and TXT previews are not supported.</li><li>File cataloging support and file data preview are separate capabilities; confirm the supported file types for the specific connector.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">Can selective report crawling be used with Power BI?</td><td valign="top"><ul><li>Selective report crawling is not currently supported.</li><li>Delta crawling is available for Power BI. It avoids fetching subreports, PBIX files, and associated metadata when the main report has not changed since the previous crawl.</li><li>Delta crawling is not the same as selecting individual reports for crawling.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">What does Delta crawling do for Power BI?</td><td valign="top"><ul><li>Delta crawling checks whether the main report has changed since the previous crawl.</li><li>When the report has not changed, the connector avoids fetching associated subreports, PBIX files, and other related metadata.</li><li>This can reduce unnecessary processing compared with fetching all associated content on every crawl.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">Can cataloged objects be deleted directly from the application?</td><td valign="top"><ul><li>For connectors that synchronize source objects during a recrawl, removed objects may be deactivated after they are removed from the source and a fresh crawl completes.</li><li>Some connectors do not provide direct deletion of crawled metadata from the application.</li><li>Filtering and removal behavior depends on the connector, so review the connector-specific instructions before changing source content.</li></ul></td></tr><tr><td valign="top">5</td><td valign="top">Can JSON and XML files be cataloged?</td><td valign="top"><ul><li>JSON and XML do not require a separate database connector in the described file connector approach.</li><li>Cataloging can work when these files are stored in a supported file location, such as S3 or an NFS accessible location.</li><li>Supported operations depend on the file connector and the required metadata or preview capability.</li></ul></td></tr><tr><td valign="top">6</td><td valign="top">Are images supported by the file connector?</td><td valign="top"><ul><li>Image files can be cataloged when stored in S3 or an NFS accessible location, according to the reviewed support assessment.</li><li>Image cataloging does not mean that image content can be profiled or previewed in every case.</li><li>Confirm the required operation and file connector before implementation.</li></ul></td></tr><tr><td valign="top">7</td><td valign="top">Can a SharePoint site that uses a /teams/ address be crawled?</td><td valign="top"><ul><li>The current SharePoint connector searches for sites under /sites/ and does not support /teams/ site paths.</li><li>Entering a /teams/ path or a full Teams site URL in the Site field does not change this behavior.</li><li>Sites using /sites/ continue to work, subject to normal connection and permission requirements.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Connector Setup" %}

<table><thead><tr><th width="58.48046875" valign="top">S. No</th><th width="168.73828125" valign="top">Question</th><th width="438.02734375" valign="top">Answer</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">How can connector compatibility be confirmed for a specific product or version?</td><td valign="top"><ul><li>Confirm the exact product name and version or release.</li><li>Identify whether the product is a standard implementation or a compatible or derived implementation.</li><li>For compatible products, identify the API or compatibility layer in use.</li><li>Share official technical documentation and details of custom configurations.</li><li>Confirm the deployment model, network restrictions, private endpoints, VPNs, firewalls, and allowlists.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">Does a connector for one product automatically support a compatible product?</td><td valign="top"><ul><li>No. Protocol or query compatibility does not guarantee that every connector feature works.</li><li>Product versions may differ in SQL behavior, APIs, endpoints, authentication, or deployment architecture.</li><li>Compatibility must be validated against the specific product version and required use cases.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">What is needed before requesting a new connector?</td><td valign="top"><ul><li>Identify the source product, version, deployment type, and business use cases.</li><li>List the objects and metadata required, expected crawl frequency, and lineage needs.</li><li>Provide official documentation, API or driver details, sample metadata, and access to a representative environment when available.</li><li>The technical team reviews feasibility, validates key use cases, confirms scope, and then estimates effort and timeline.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">Can a custom connector be developed for an unsupported application?</td><td valign="top"><ul><li>Yes, subject to technical assessment and source type.</li><li>The public Connector SDK supports application connectors that crawl metadata and data.</li><li>Reporting, ETL, and file system connectors are not currently covered by the public SDK and may require OvalEdge-led development.</li><li>The usual process includes requirements gathering, feasibility review, proof of concept, scope confirmation, development, testing, and documentation.</li></ul></td></tr><tr><td valign="top">5</td><td valign="top">Where is the public Connector SDK documentation available?</td><td valign="top"><ul><li>The SDK and Getting Started guide are available at https://github.com/ovaledge/oe_csp_sdk.</li><li>Product documentation is available at https://docs.ovaledge.com/.</li><li>The public SDK scope is limited to application connectors; other source types may require a separate development engagement.</li></ul></td></tr><tr><td valign="top">6</td><td valign="top">Does the S3 connector support non AWS or on premises S3 compatible storage?</td><td valign="top"><ul><li>No. The current S3 connector does not support custom endpoints or non-AWS S3 backends.</li><li>AWS S3 connection setup uses the configured region and the AWS authentication flow.</li><li>A nonstandard region or a location response that does not map to a supported AWS region will not work.</li></ul></td></tr><tr><td valign="top">7</td><td valign="top">Can the S3 connector work without AWS STS?</td><td valign="top"><ul><li>No. The current AWS S3 connection validation uses STS to retrieve the AWS account ID.</li><li>The current implementation does not provide a supported no-STS mode.</li></ul></td></tr><tr><td valign="top">8</td><td valign="top">Can one region be used for buckets in different AWS regions?</td><td valign="top"><ul><li>Provide the correct region for each bucket when buckets are located in different regions.</li><li>A single fixed region is not appropriate for buckets that belong to different regions.</li></ul></td></tr><tr><td valign="top">9</td><td valign="top">Is SingleStore officially supported through the MySQL connector?</td><td valign="top"><ul><li>SingleStore is not officially supported in the reviewed assessment.</li><li>MySQL protocol compatibility does not confirm metadata compatibility.</li><li>Validate the required metadata queries, routine definitions, and permissions against the exact SingleStore version before relying on the connector.</li></ul></td></tr><tr><td valign="top">10</td><td valign="top">What permission is required to retrieve MySQL routine definitions?</td><td valign="top"><ul><li>For MySQL version 8.0.20 or later, the reviewed technical response states that SHOW_ROUTINE is sufficient for the service account to retrieve procedure definitions.</li><li>The exact SQL commands and permission requirements should be confirmed against the supported MySQL version and connector operations.</li><li>This permission guidance does not confirm equivalent behavior in SingleStore.</li></ul></td></tr><tr><td valign="top">11</td><td valign="top">Is Percona MySQL confirmed as compatible?</td><td valign="top"><ul><li>Compatibility has not yet been confirmed through environment testing.</li><li>Identify whether the deployment uses standalone Percona Server or Percona XtraDB Cluster and record the exact version.</li><li>For a clustered deployment, validate query log visibility across nodes before confirming compatibility.</li></ul></td></tr><tr><td valign="top">12</td><td valign="top">Can Percona MySQL replace standard MySQL for an OvalEdge deployment?</td><td valign="top"><ul><li>Compatibility has not been confirmed through testing.</li><li>The technical assessment must distinguish between standalone Percona Server and Percona XtraDB Cluster and record the exact version.</li><li>A local environment test is required before confirming compatibility, particularly where query logs are accessed across cluster nodes.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Lineage" %}

<table><thead><tr><th width="59.296875" valign="top">S. No</th><th width="169.4140625" valign="top">Question</th><th width="447.49609375" valign="top">Answer</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">What is automatic lineage?</td><td valign="top"><ul><li>Automatic lineage identifies how data moves and changes between supported source systems, transformation tools, databases, and reporting tools.</li><li>Depending on the connector and source metadata, lineage can show relationships at the table and column level.</li><li>Lineage availability varies by connector and may require an add-on or a separate lineage build job.</li></ul></td></tr><tr><td valign="top">2</td><td valign="top">Does every standard connector include automatic lineage?</td><td valign="top"><ul><li>No. A standard connector collects supported metadata from a source system.</li><li>Automatic lineage is an additional capability for supported connectors and use cases.</li><li>The supported connector documentation identifies the available lineage capabilities and limitations.</li></ul></td></tr><tr><td valign="top">3</td><td valign="top">Can OvalEdge build lineage from YAML files?</td><td valign="top"><ul><li>YAML lineage parsing is not available out of the box.</li><li>A custom solution may be evaluated after reviewing sample files, their structure, storage location, ETL platform, and transformation logic.</li><li>Feasibility and accuracy must be assessed before confirming a solution.</li></ul></td></tr><tr><td valign="top">4</td><td valign="top">Can OvalEdge extract lineage from custom Java code?</td><td valign="top"><ul><li>Native automatic lineage extraction from Java code is not currently supported.</li><li>An AI-based approach may be explored, but complete accuracy cannot be guaranteed.</li><li>The required source code, expected lineage, and acceptable accuracy should be reviewed before any custom work.</li></ul></td></tr><tr><td valign="top">5</td><td valign="top">Can OvalEdge build lineage from SSAS model files without a live connection?</td><td valign="top"><ul><li>The current SSAS connector uses model files such as ASDATABASE files for lineage building.</li><li>The files do not currently provide file-based metadata crawling through the connector.</li><li>Profiling requires live access to the SSAS model.</li></ul></td></tr><tr><td valign="top">6</td><td valign="top">Why might a supported database table be missing from lineage?</td><td valign="top"><ul><li>The related database may not yet be cataloged through its own connector.</li><li>Lineage may use a temporary table name until the source or target database is cataloged.</li><li>Catalog the related database and rebuild lineage to resolve the object reference, where supported.</li></ul></td></tr><tr><td valign="top">7</td><td valign="top">What is needed to assess lineage for a pilot connector such as Domo?</td><td valign="top"><ul><li>The feasibility assessment reviews existing connector capabilities, available APIs and metadata, and the requested lineage scenarios.</li><li>Access to a test environment or representative sample data may be required.</li><li>An effort estimate can be provided after feasibility and scope are understood; the timeline depends on complexity.</li></ul></td></tr><tr><td valign="top">8</td><td valign="top">Does the Salesforce connector support Auto Lineage?</td><td valign="top"><ul><li>Auto Lineage is currently unsupported for Salesforce because the available cataloged objects do not provide sufficient information to capture data flows.</li><li>Support for lineage through Apex methods and triggers may be considered in the future, but it is not confirmed as a current capability.</li></ul></td></tr><tr><td valign="top">9</td><td valign="top">Why is Salesforce Data Quality coverage limited?</td><td valign="top"><ul><li>Salesforce data is retrieved through SOQL and REST APIs rather than standard SQL queries.</li><li>Nested and custom object types, along with the lack of aggregate functions, limit profiling and Data Quality capabilities compared with SQL-based systems.</li></ul></td></tr><tr><td valign="top">10</td><td valign="top">Can OvalEdge derive lineage from custom Java or Spark transformations?</td><td valign="top"><ul><li>Native automatic lineage extraction from custom Java and Spark code is not currently supported in the reviewed assessment.</li><li>Custom development may be technically assessable, but feasibility and prior implementation are not confirmed by the source information.</li><li>Representative code, expected lineage, and transformation details are needed for an assessment.</li></ul></td></tr><tr><td valign="top">11</td><td valign="top">Why can profiling take a long time?</td><td valign="top"><ul><li>Profiling duration depends on the number of objects, table sizes, total data volume, selected profiling attributes, and whether full or sample profiling is selected.</li><li>Profiling a large source can take longer and may place additional load on the source system.</li><li>Review the required profiling scope and schedule, and share job logs with support if processing remains unexpectedly slow.</li></ul></td></tr><tr><td valign="top">12</td><td valign="top">Can Snowflake Data Metric Function results be displayed in OvalEdge?</td><td valign="top"><ul><li>Support for reading and displaying Snowflake Data Metric Function results requires technical validation against the required OvalEdge version and connector configuration.</li><li>The expected use case is to associate results with the corresponding catalog tables or columns.</li><li>An API based approach may also be assessed if direct retrieval is not suitable.</li></ul></td></tr><tr><td valign="top">13</td><td valign="top">Can custom Data Quality integrations use APIs?</td><td valign="top"><ul><li>OvalEdge APIs are one option for custom Data Quality integrations.</li><li>Other options identified in the technical assessment include LMDF, MCP, and AskEdgi.</li><li>The suitable approach depends on where the rules run, how results are represented, and how results must map to catalog objects.</li></ul></td></tr><tr><td valign="top">14</td><td valign="top">Does the Apache Airflow connector support Python based DAG lineage?</td><td valign="top"><ul><li>The connector catalogs DAGs and tasks.</li><li>Automatic lineage for Python-based DAGs is not supported in the reviewed assessment.</li><li>For SQL-based DAGs, AI-augmented lineage can generate automatic lineage.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.3/connectors/troubleshooting-and-faqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.