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

# Week of February 22 – 28, 2026

> What's new this week: clearer, more specific errors when credentials don't work, tougher retry behavior on busy vendor APIs, and steadier Microsoft 365 syncs on large tenants.

<Tabs>
  <Tab title="Platform" icon="layer-group">
    <Info>
      **Platform is the composable core of Parable.** Everything here has been seen across enough customers, long enough, that we're confident it behaves the same way for yours. We move things into Platform deliberately — a great composable platform takes patience to build, and we'd rather be right than fast at this layer. If something's in Platform, it's production, stable, and ours to keep steady.

      <br />

      **How to read Platform results:** this is the bedrock.
    </Info>

    ### <Icon icon="sparkles" /> New

    <AccordionGroup>
      <Accordion title="Clearer, more specific errors when credentials don't work" icon="key" defaultOpen>
        <Badge>Direct impact</Badge>

        * When you connect a new vendor and the credentials don't work, Parable now tells you **why** — specifically, whether the credentials are wrong ("don't have permission, edit configuration") or whether something broke on our side ("something went wrong — reach out to Parable").
        * Each message comes with a stable identifier that helps our team jump straight to the right fix when you reach out.
        * The error shows up on both steps of the connection wizard — so if you hit a problem, you can see exactly where it happened.
      </Accordion>

      <Accordion title="Automatic retries when a vendor's API is under pressure" icon="rotate-right">
        * If a connected vendor's API returns a rate-limit signal or a temporary server error, Parable now backs off automatically and retries with increasing delays — no action needed on your side.
        * We also classify failures under the hood so we know whether to retry, move on, or surface a genuine error. Fewer transient failures will surface to you as sync errors.
      </Accordion>

      <Accordion title="Steadier Microsoft 365 syncs on large tenants" icon="microsoft">
        * Microsoft 365 syncs on large workspaces previously hit gateway timeouts when pulling a long history of messages, calendar events, or sign-in logs in one request.
        * Parable now breaks those long time ranges into manageable chunks automatically — so syncs finish instead of stalling.
        * We also tightened the **default set** of Microsoft taps to the ones that work on most tenants' permissions out of the box (messages, calendar, teams) — audit and sign-in log taps can still be enabled when your admin has granted the required permissions.
      </Accordion>

      <Accordion title="Broader support for enterprise-style OAuth" icon="lock">
        * Parable now supports service-to-service OAuth2 (Client Credentials) out of the box on our new sync framework.
        * In practical terms: more enterprise APIs can be connected without custom work.
      </Accordion>

      <Accordion title="Support for vendors that use async download jobs" icon="hourglass-half">
        * Some vendor APIs make you start a job, wait for it to finish, and then download the result — Parable now handles that pattern natively instead of engineering per-connector.
        * You won't notice this directly; it's the groundwork that lets us ship new connectors faster.
      </Accordion>
    </AccordionGroup>

    ### <Icon icon="arrow-trend-up" /> Improved

    <AccordionGroup>
      <Accordion title="Faster, clearer support when something breaks" icon="headset">
        * Under the hood, Parable now ships structured logs for our data-transformation pipelines with proper severity, so the right alerts fire at the right time and false alarms get filtered out.
        * When you report an issue, our team has more context from the first message — less back-and-forth, faster fixes.
      </Accordion>

      <Accordion title="Sync telemetry you can rely on" icon="chart-line">
        * How many bytes a sync wrote, how many taps finished, and how many were in scope — all of those numbers now land correctly on every sync job.
        * Visible today in our admin tooling; surfaces to you in Parable's own dashboards as they come online.
      </Accordion>

      <Accordion title="Light theme polish + small UI improvements" icon="paintbrush">
        * Light mode moved to a neutral gray palette — cleaner, more readable, and no more "is that pink?" moments when switching themes.
        * The page title on sign-in screens is less cluttered, modal backdrops render correctly on first paint, and theme switching no longer flashes.
        * We renamed "Vendors" to "Connectors" across the app to match the rest of our product language.
      </Accordion>
    </AccordionGroup>

    ### <Icon icon="wrench" /> Fixed

    <AccordionGroup>
      <Accordion title="Microsoft 365 data pipeline fixes" icon="database">
        * Resolved a set of edge cases where Microsoft 365 transforms didn't flow cleanly into Parable's reporting layer — typically on tenants with partial permissions or unusual volume.
        * If you've been waiting on that data, you should see it populating correctly now.
      </Accordion>

      <Accordion title="End-to-end ingestion-to-transformation glue" icon="workflow">
        * A batch of small fixes along the path from source-data ingestion to transformed analytics-ready tables: case-consistent credential handling, correct deployment names per tenant, and resilient rate-limit handling.
        * Each one was a quiet failure mode before; together they mean the pipeline actually holds together.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Preview" icon="flask">
    <Info>
      **Preview is where we put features we're confident in, but haven't yet seen at full scale across every organization.** The most common reason: the AI models from Google, OpenAI, and Anthropic that underpin classification update on their own schedule, and the methods we layer on top learn your organization over time. That means Preview results can shift slightly week-to-week — **within a margin of error, rarely enough to flip a decision you'd make from them.** When we've seen consistent results across enough organizations for long enough, a Preview feature graduates to **Platform**.

      <br />

      **How to read Preview results:** decision-ready with an honest caveat. We'll tell you when the methodology under a Preview feature changes.
    </Info>

    ### <Icon icon="sparkles" /> New

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No Preview-specific changes this week.
    </Card>

    ### <Icon icon="arrow-trend-up" /> Improved

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Nothing to call out in Preview this week.
    </Card>

    ### <Icon icon="wrench" /> Fixed

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No Preview-specific fixes this week.
    </Card>
  </Tab>

  <Tab title="Labs" icon="flask-vial">
    <Info>
      **Labs is where we deliver insights tailored to your organization faster than our main roadmap would allow.** A Labs report is built for your team specifically, leans on the newest AI capabilities, and may ship with less visual polish than the rest of Parable — because the value is in the insight, not the chrome. Results may evolve as the underlying models improve; that's intentional — we're moving with the frontier, not chasing it. Once a Labs capability proves itself across several organizations, it graduates to **Preview**.

      <br />

      **How to read Labs results:** directional.
    </Info>

    ### <Icon icon="sparkles" /> New

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No Labs-specific shipments this week.
    </Card>

    ### <Icon icon="arrow-trend-up" /> Improved

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Nothing Labs-specific this week.
    </Card>

    ### <Icon icon="wrench" /> Fixed

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Nothing Labs-specific this week.
    </Card>
  </Tab>
</Tabs>

***

<Note>
  **How we tier releases:** [Labs](/release-tiers#labs) · [Preview](/release-tiers#preview) · [Platform](/release-tiers#platform). The world — and the AI beneath every intelligent product — is changing faster than ever. We ship you the latest and greatest. Occasionally your results will shift as models and methods refine; rarely enough to flip a decision, always with a note from us when the change is meaningful.
</Note>

<Tip>
  Want a closer look at any of these? Reach out to your Parable team — we're happy to walk you through what shipped and what's coming next.
</Tip>