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

# Troubleshoot Microsoft Fabric

> Resolve common Microsoft Fabric connection, discovery, schema, permission, and query issues.

<AccordionGroup>
  <Accordion title="The workspace or GraphQL API is not listed">
    Langdock can discover workspaces and APIs that are visible to the signed-in Microsoft account. Check the user's Fabric access. If the user has direct access to one API instead of access to its workspace, copy the full GraphQL endpoint URL from Fabric and include it in the request.
  </Accordion>

  <Accordion title="The schema cannot be retrieved">
    Enable introspection in the GraphQL API settings and confirm that the signed-in user can access the API. After changing source objects, update the API schema in Fabric before trying again.
  </Accordion>

  <Accordion title="Sign-in succeeds but execution is denied">
    Confirm that the user has **Run Queries and Mutations** on the GraphQL API. For an API using SSO, check the user's source permissions. For an API using Saved credentials, check the saved identity's source permissions.

    If the Langdock workspace enabled additional Fabric actions after the connection was created, reconnect the Microsoft account once to grant any newly required OAuth scopes.
  </Accordion>

  <Accordion title="Expected fields or objects are missing">
    Add the objects to the GraphQL API and update its schema in Fabric. Then ask Langdock to inspect the schema again.
  </Accordion>

  <Accordion title="Some users see different rows">
    With SSO, Fabric evaluates source permissions and security rules for the signed-in user. Verify the result directly in Fabric as the affected user.
  </Accordion>

  <Accordion title="All users see the same source data">
    Check whether the GraphQL API uses Saved credentials. In that mode, Fabric evaluates source access as the saved identity rather than the individual caller.
  </Accordion>

  <Accordion title="A mutation is rejected">
    Confirm that the API schema exposes the operation as a mutation and that the applicable source identity has permission to perform the change. Test the same mutation in Fabric's GraphQL editor with a disposable record.
  </Accordion>

  <Accordion title="A result is too large">
    Ask for fewer fields, add filters or server-side aggregation, or retrieve smaller pages. For a full export, ask Langdock to return the result as a JSON file.
  </Accordion>

  <Accordion title="Fabric is throttled or its capacity is unavailable">
    Wait and try the read request again. Langdock does not automatically retry mutations. If the issue persists, ask the Fabric capacity admin to investigate it in the [Capacity Metrics app](https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app).
  </Accordion>
</AccordionGroup>

## Advanced Fabric administration

For environment promotion, source binding, networking, and current platform restrictions, use Microsoft's documentation as the source of truth:

* [Source control and deployment pipelines for API for GraphQL](https://learn.microsoft.com/en-us/fabric/data-engineering/graphql-source-control-and-deployment)
* [Fabric API for GraphQL limitations](https://learn.microsoft.com/en-us/fabric/data-engineering/api-graphql-limits)
* [Fabric API for GraphQL FAQ](https://learn.microsoft.com/en-us/fabric/data-engineering/graphql-faq)