In this workshop
When a code-native integration fails, the whole run shows up as a single step: one error and whatever the developer thought to log. Support can see that it failed, but not where. And the ticket is routed to whoever wrote the code.
In this workshop, Taylor Reece shows how execution sections give code-native runs the step-by-step visibility low-code has always had. Name the parts of your integration logic, and anyone on your team can see which ones ran, which one failed, and the logs behind it. He also walks through the rebuilt executions list and detail views, and shows why a structured run is the foundation for AI to read an execution and tell you what went wrong.
Walk away knowing how to
- Add execution sections to a code-first (code-native) integration with two calls in the Prismatic SDK
- Read a code-first (code-native) run as an ordered timeline of sections with status, timing, and logs
- Find the execution behind a customer report by filtering on trigger payload, flow, status, and date range
- Diagnose a failure from a plain-language error, then replay fixed executions in bulk
- Structure your runs so AI-assisted debugging has something to read
