December 9

Connectors

View logs directly in the Agent Component

You can now access execution logs directly in the Agent Component, without switching to the Execution Panel.

In Output Details, you’ll find grouped logs such as Configuration, Input, User, System, Tool Call, and Input/Output Guardrail.

This update gives you quicker visibility into what happened during execution and makes it easier to validate or troubleshoot your Agent.

Learn more

Platform Improvements

Reference trigger inputs using Double Braces

You can reference the execution data sent to the trigger using Double Braces ({{ trigger.input }}).

This reduces complexity and simplifies pipeline construction, without relying on Session Management.

Read the documentation

Documentation

We’ve created the following use case documentation to help you explore the Platform through practical, real-world examples:

• How to apply JOLT for JSON transformations

• Building basic JOLT transformations

• Understanding JOLT operators

• Building advanced JOLT transformations

• Applying JOLT to practical use cases

• How to integrate Distribution Centers using Multi-Instance

Bug fixes

• Pipelines not saved inside the chosen folder: We fixed a bug that prevented pipelines from being saved in the folder where they were created, placing them in the project root instead.

• Major versions saved in the wrong project: We fixed a bug that caused the major version of a pipeline to be saved in a different project instead of the one selected.

• Mouse cursor changing focus: We fixed a bug that caused the mouse cursor to jump to the beginning of the field at random while editing connector configuration forms.

• Problem using the Step Alias with the ISNULL function: We fixed a bug that caused Double Braces expressions to be evaluated incorrectly when using Step aliases, making Choice branches and ISNULL() behave inconsistently.

• Top Connectors offenders chart is intermittent: We fixed a bug that caused the Top Connectors offenders chart to intermittently display missing or outdated data.

• Visual bug on the Pipeline logs page: We fixed a bug that caused some logs to not render correctly on the Pipeline Logs page, preventing users from seeing all the events needed to troubleshoot pipeline execution issues.