July 29

New Consumption-Based Model page

We’ve upgraded the Consumption-Based Model page on the Digibee Integration Platform to give you a clearer, more actionable view of your usage. With improved data visualization, and cost breakdowns, you can now monitor and manage your consumption more efficiently across all environments.

Learn more about the Consumption-Based Model.

Latency metrics in the Monitor Overview page (General Availability)

The Monitor Overview chart has been enhanced with new latency metrics, allowing you to better understand how quickly your pipelines respond to requests. By selecting a specific pipeline and time range, you can now view performance insights such as p50, p90, p95, p99, and average execution time — helping you identify issues more quickly.

Access the Monitor overview documentation.

Previous Steps Access now available for Capsules (General Availability)

You can now use the Previous Steps Access feature in two ways: to reference outputs from a capsule within a pipeline, and also while building a new capsule. This allows you to access data across steps using Double Braces ({{ step.alias.<jsonpath> }}), without relying on Session Management.

Learn more about Previous Steps Access.

JMS Trigger: Support for Assume Role in SQS with AWS V4 account

The JMS Trigger now supports Assume Role configuration when using the SQS queue type with an AWS V4 account. Three new parameters were added:

• Role ARN

• Role Session Name

• Expiration (in ms)

These fields enable the use of temporary security credentials to access the SQS queue. The Role ARN specifies the IAM Role to be assumed, the Role Session Name identifies the session for auditability, and the Expiration sets the duration of the temporary token.

Further information can be found in the JMS Trigger documentation.

Documentation

We’ve updated the following documentation:

• How to set up Digibee API metrics with Datadog

• Highly scalable ETL model for Digibee

• Pipeline version history

Improvements and bug fixes

Improvements

• AI Assistant: To improve usability, we’ve updated the message and added a “Save pipeline” button directly in the AI Assistant for cases where it’s opened before saving the pipeline.

Bug fixes

• Disabled “Redeploy” button: We fixed a bug that kept the “Redeploy” button disabled until a change was made in the sidesheet, preventing the redeployment of unchanged versions.

• Error when updating alert metrics: We fixed a bug that caused an error when users tried to update an alert’s metric, preventing changes from being saved.

• AI Assistant behavior corrections: We fixed a bug that duplicated messages when the chat was opened and another that caused it to get stuck in an infinite loading state.

• Search button in Pipeline Logs not returning recent data: We fixed a bug that prevented the Monitor's search button from retrieving the most recent log data. Users had to refresh the page to see updated results for the last few minutes.

• Double Braces not working in “From” parameter on Email V2 connector: We fixed a bug that prevented the use of Double Braces in the “From” parameter on Email V2 connector.