Prospector Studio Release 2026.10.09 — Workflow, Scheduling & Code Mode Reliability

Studio

Fixed: MCP server configuration now displays correctly. Some connected MCP tool installations showed a blank configuration screen even though their settings were saved correctly, making it look like the configuration had been lost. The configuration screen now displays the saved settings correctly.

Fixed: pinning a chart to your dashboard now works reliably. Clicking "Pin Chart to Dashboard" on a chart could sometimes fail with an error, even for charts that displayed correctly on screen. Chart pinning is now more reliable across the ways charts can appear in a conversation.

Code Mode & Snippets

Fixed: MCP tools now work reliably in Code Mode. Personas with a standalone connected tool (such as Devo) could fail on every call when used from Code Mode, even though the same tool worked fine in normal chat. This is fixed — Code Mode now reaches these tools the same way chat does.

Fixed: editing a snippet no longer creates a duplicate file. Saving changes to certain snippets could silently create a second, duplicate-looking file instead of updating the original — leaving the edit seemingly lost and cluttering the snippet list with look-alike entries. Saving now correctly updates the original file.

Fixed: long-running code executions now report a clear timeout instead of a generic error. A code-mode execution that ran long (a slow query, a long tool chain) could fail with an opaque, unhelpful error instead of a clear timeout message. Long executions now return a proper "timed out" result, so it's clear what happened.

Improved: plain-JavaScript steps in Workflow Builder are now viewable and editable. Workflow steps written as plain JavaScript ran correctly but couldn't be viewed or edited in the Builder interface — they appeared as a blank, unusable panel. The Builder now shows and lets you edit this type of step directly, alongside the existing options.

Workflows

Fixed: workflows with two independent parallel branches no longer silently drop results. Workflows containing two separate branch sections could lose the entire output of one branch while still reporting the run as fully successful — with no error shown anywhere. This is fixed: both branches now evaluate and report correctly, so downstream reports, cases, and notifications receive complete data.

Fixed: the workflow builder no longer saves an incomplete data connection. If a workflow step's input was connected to a source but no specific field was selected, the builder could save that connection anyway — causing it to silently resolve to an empty value when the workflow ran. The builder now prevents this from being saved in a broken state.

Scheduled Jobs

Fixed: scheduled jobs could silently stop running for some tenants. For tenants with certain access-control settings enabled, scheduled (cron) jobs stopped running entirely — with no record of the failed attempt, so the issue was invisible from the UI. Scheduled jobs now run correctly under these settings.