> ## 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 March 1 – 7, 2026

> What's new this week: clearer connector status in the app, automatic retries when a vendor is busy, and reliability investments that set us up for what's coming next.

<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 useful connector status in the app" icon="heart-pulse" defaultOpen>
        <Badge>Direct impact</Badge>

        * The connector cards now show what your connector is actually doing — syncing, queued, paused, needs credentials, or healthy and idle — instead of a single catch-all "connected" badge.
        * Makes it obvious at a glance whether data is flowing, and gives you (and us) a better starting point when something looks off.
      </Accordion>

      <Accordion title="Automatic retries when a vendor's API is busy" icon="rotate-right">
        * If a connected vendor's API asks Parable to slow down, Parable now backs off and retries on its own — no action needed on your side.
        * You'll see fewer transient sync failures during heavy-traffic windows.
      </Accordion>

      <Accordion title="New sources Parable can connect to" icon="plug">
        * **TestRail** connects natively.
        * Behind-the-scenes support added for **Okta**, **Zoom**, and **GitLab** long backfills, so connectors built on those sources behave more predictably out of the gate.
      </Accordion>

      <Accordion title="Clearer error messages when a backfill range is invalid" icon="circle-alert">
        * If you request a backfill that's out of range for a given source, you'll now see a specific message explaining *why* instead of a silent failure.
      </Accordion>
    </AccordionGroup>

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

    <AccordionGroup>
      <Accordion title="Smarter, more flexible data syncing" icon="calendar-days">
        * Connectors now have a first-class daily schedule, automatic first-sync backfill, and better handling of large historical windows (chunked so they don't time out).
        * Net effect: you get data flowing sooner after you connect, and long backfills are more likely to finish cleanly the first time.
      </Accordion>

      <Accordion title="Stronger protection for your credentials" icon="shield-check">
        * Credentials you enter (API keys, tokens, OAuth secrets) now flow through a stricter path: encrypted in your browser before they leave, stored in a dedicated secret-management service, and redacted from every response.
        * Updating part of a connector's config no longer risks wiping credentials you set earlier — the new update path merges on top of what's already there.
      </Accordion>

      <Accordion title="Behind-the-scenes infrastructure hardening" icon="server">
        * Production infrastructure got backups, tighter permissions, and smoother deploys this week.
        * You shouldn't notice any of it day-to-day — that's the point. It's the groundwork for the observability and reliability improvements landing over the next few weeks.
      </Accordion>
    </AccordionGroup>

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

    <AccordionGroup>
      <Accordion title="Tightened the safety rails on connector updates" icon="circle-check">
        * Closed a class of edge cases where certain connector configuration updates could behave unexpectedly. You may have never seen this; it's fixed either way.
      </Accordion>

      <Accordion title="Small visual polish across the app" icon="paintbrush">
        * Minor icon-alignment fix inside the design system — the kind of thing you stop noticing once it's right.
      </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 new Preview features this week.
    </Card>

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

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Nothing Preview-specific this week — the focus was on Platform-layer foundations that Preview features will lean on shortly.
    </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 new Labs capabilities shipped this week.
    </Card>

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

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      Your Labs experience is unchanged this week — watch this space.
    </Card>

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

    <Card icon="cookie-bite" title="We're cooking something good ;)">
      No Labs fixes 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>