- Platform
- Preview
- Labs
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.
How to read Platform results: this is the bedrock.
New
Clearer, more specific errors when credentials don't work
Clearer, more specific errors when credentials don't work
Direct impact
- 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.
Automatic retries when a vendor's API is under pressure
Automatic retries when a vendor's API is under pressure
- 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.
Steadier Microsoft 365 syncs on large tenants
Steadier Microsoft 365 syncs on large tenants
- 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.
Broader support for enterprise-style OAuth
Broader support for enterprise-style OAuth
- 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.
Support for vendors that use async download jobs
Support for vendors that use async download jobs
- 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.
Improved
Faster, clearer support when something breaks
Faster, clearer support when something breaks
- 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.
Sync telemetry you can rely on
Sync telemetry you can rely on
- 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.
Light theme polish + small UI improvements
Light theme polish + small UI improvements
- 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.
Fixed
Microsoft 365 data pipeline fixes
Microsoft 365 data pipeline fixes
- 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.
End-to-end ingestion-to-transformation glue
End-to-end ingestion-to-transformation glue
- 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.
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.