New Executions Experience: Troubleshoot Integrations without Engineering

Prismatic has introduced a redesigned execution-visibility experience intended to help support, customer success, operations, and developers diagnose integration failures without relying solely on the original builder. The release separates execution search and analysis into a filterable list view and a dedicated detail view, allowing users to find runs by trigger-payload data, flow, status, time range, and combined conditions across a 14-day retention period, then bulk replay failed executions when appropriate. Detail pages present plain-language errors, step-by-step timelines, branch and loop activity, collapsed retries and batches, logs, outputs, trigger payloads, and shareable execution links. For code-first integrations, optional SDK-based execution sections let developers organize onExecution logic into named, timed segments whose logs and outcomes can be inspected individually. The broader visibility updates include aggregate health charts and drill-downs across organizations, integrations, instances, and customers, while log search now covers the full retention window and exposes trigger payloads and step results. The capabilities are available without opt-in or price changes for low-code and code-first integrations, although execution sections require the latest Prismatic SDK and newly completed runs may take about a minute to appear in the list.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.