> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Common questions about the Sigma connector.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Sigma FAQ",
            "description": "Common questions about the Sigma connector.",
            "url": "https://docs.dqlabs.ai/sources/sigma/faq",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

## Connector Lifecycle

<AccordionGroup>
  <Accordion title="What happens if I delete a connector?">
    Deleting a source triggers an approval workflow based on your organization's settings. Once approved, the source and all associated metadata are permanently deleted. The deletion cannot be undone after approval.
  </Accordion>

  <Accordion title="What happens to existing data and alerts if a connector is paused or disconnected?">
    Existing metadata, quality scores, and alerts are retained while the connector is inactive. No new data is collected until the connector is re-enabled. If the connector is permanently deleted (after approval), all associated data is removed.
  </Accordion>

  <Accordion title="How long does Prizm retain historical data?">
    The default data retention window for time-series observability data, quality score history, and usage history is **90 days**.
  </Accordion>

  <Accordion title="How does manual re-sync work alongside scheduled jobs?">
    Triggering a manual scan runs the job immediately without affecting the configured schedule. Any schedule update overrides the existing schedule and applies to all future executions.
  </Accordion>
</AccordionGroup>

## Sigma-Specific

<AccordionGroup>
  <Accordion title="Why are Usage and Reliability metrics missing for my Workbooks?">
    Those metrics depend on Sigma's audit/query log access, which requires a **Premier-tier** Sigma account with logging enabled. If your account doesn't have that access, Prizm doesn't approximate these metrics — they simply won't populate until log access is available.
  </Accordion>

  <Accordion title="Does the connector support OAuth?">
    Yes, for enterprise deployments already using GCP IAP, via HashiCorp Vault with automatic token refresh. Client ID + Client Secret is the recommended path for most service-to-service connections; Sigma does not support standalone username/password API access in production.
  </Accordion>

  <Accordion title="How is lineage resolved for a Workbook with no Dataset?">
    When a Workbook queries the warehouse directly rather than through a Sigma Dataset, Prizm resolves lineage from Sigma Logs API query records instead of Dataset metadata.
  </Accordion>

  <Accordion title="Are calculated fields tracked for changes?">
    Yes. A formula diff between consecutive catalog runs is treated as schema drift and raises a Medium-severity alert, distinct from a full schema change on the underlying warehouse table.
  </Accordion>

  <Accordion title="Is there a Sigma-specific analytics dashboard or Chrome extension?">
    Not yet. Dedicated Sigma Catalog/Quality/Observability views are gated on Prizm's Dynamic Dashboards work, and the Sigma Chrome Extension and catalog integrations (Alation, Atlan, Azure Purview) are on the roadmap but not part of this release.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Troubleshooting" icon="wrench" href="/help/troubleshooting">
    For connection errors, permission issues, and performance problems.
  </Card>

  <Card title="Glossary" icon="circle-question" href="/help/glossary">
    For definitions of terms used in this FAQ.
  </Card>
</CardGroup>