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

Early Access experience is live end-to-end

Direct impact
  • New customers invited into Early Access now see a dedicated pre-labs experience the moment they sign in — sidebar, permissions, and landing page all line up automatically.
  • Existing customer navigation is unchanged.
  • Every error surface — in the app, in the SDKs you build on, and in webhook responses — now carries a stable, machine-readable code alongside the message.
  • Easier for you to automate on; faster for our team to jump to the right fix when you reach out.
  • If you need a source we don’t yet support, you can now submit the request from inside Parable instead of emailing your rep.
  • Requests land in our internal triage queue so we can scope and prioritise them consistently.
  • Administrators can now add new users and remove departed ones directly from the admin app.
  • No more “can your Parable contact run this for me” tickets for routine access changes.

​
Improved

  • Behind the scenes, every request through Parable now carries a shared trace identifier from the frontend through the API into ingestion and the database.
  • When you report something, our team has end-to-end context from the first message — shorter back-and-forth, faster fixes.
  • Cleaner login and early-access experience.
  • Donut-chart visualisations used across the product now support drill-down and render more reliably on dense views.
  • A handful of smaller alignment + interaction fixes in the connector setup flow.
  • Ingestion and transformation schedules now share a single unified engine, so schedule changes behave consistently across both.
  • Schedules left behind by a removed connector are cleaned up automatically.

​
Fixed

Stuck and zombie syncs are cleaned up automatically

  • We addressed the most common reasons a sync could appear “in progress” forever — runaway timeouts, leaked worker slots, and orphaned sub-flows.
  • If a sync ever gets interrupted now, Parable notices and clears it out instead of leaving it stuck.
  • Resolved a rate-limiting edge case on Okta that could cause sync failures during heavy windows.
  • Fixed an Okta 404 that affected the application-users feed for some workspaces.
  • Corrected a pagination issue on Microsoft 365 (Microsoft Graph) so long result sets now retrieve fully.
  • Upgraded our workflow engine to the latest patch release; replaced duplicate audit-log configurations; standardised how the platform handles pod disruptions during cluster maintenance.
  • Net effect: fewer small hiccups during deploys, more consistent behaviour during our routine infrastructure upgrades.
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.