Skip to main content
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.
How to read Platform results: this is the bedrock.

New

Clearer sign-in and auth errors with stable identifiers

Direct impact
  • When an authentication step doesn’t go as planned, you’ll now see a cleaner, more specific message both in the app and in any integrations you’ve built on Parable.
  • Each message carries a stable identifier so if you ever need to report one, our team can jump straight to the right fix.
  • Large workspaces (Slack, Microsoft 365, Google Workspace, Okta, Salesforce, GitLab, Notion, Atlassian) now run with more headroom, so big syncs finish more predictably.
  • If a sync ever gets interrupted, Parable now notices and cleans it up automatically, instead of leaving it “in progress” indefinitely.
  • Behind the scenes, Parable now tags every request with the workspace it belongs to and captures a consistent trace of what happened.
  • When you report something, our team has more context from the first message — shorter back-and-forth, faster fixes.

Improved

  • The connector directory is tidier — simpler connection-status pill, smaller connector logos, and cleaner layout across the vendor detail pages.
  • A new sort-then-group control makes it easier to keep your recently-picked filters at the top as you refine a view.
  • Labs that rely on filters, date pickers, or dropdowns now match the design language you see elsewhere in the product.
  • Small things — aligned controls, consistent checkboxes — but they add up to a less jarring jump between Parable’s main surfaces and a Lab view.
  • Labs that need to warm up a reference dataset before rendering now do so during server startup rather than on your first click.
  • If a Lab view takes a little longer than usual to build (dense charts, cross-joined data), it’ll still complete — we raised the render budget so it isn’t cut short.

Fixed

  • A batch of quiet bug fixes in Parable’s data-transformation layer. Each one removes a silent-failure mode — misrouted data, partial runs, a handful of edge cases around how timestamps and bucket paths are resolved.
  • Net effect: fewer data surprises in your Parable views.
  • A week of layered improvements closing audit findings around SSH access, database flags, IAM scoping, and audit-log retention.
  • No customer-visible change — just a stricter posture under the hood.

How we tier releases: Labs · Preview · 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.
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.