# 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](/documentation/licensing/licensing-models/consumption-based-model.md).

<figure><img src="/files/oSPNmXVPfNiSSKCZzdck" alt=""><figcaption></figcaption></figure>

## **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](/documentation/developer-guide/development-cycle/dashboards.md).

<figure><img src="/files/kK811qHPIlJS6iJe2Tzc" alt=""><figcaption></figcaption></figure>

## **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.](/documentation/connectors-and-triggers/double-braces/how-to-reference-data-using-double-braces/previous-steps-access.md)

<figure><img src="/files/tpZPMPemFN1c52Wy6P2H" alt="" width="563"><figcaption></figcaption></figure>

## **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/connectors-and-triggers/triggers/messaging-and-events/jms.md).

## **Documentation**

We’ve updated the following documentation:

* [How to set up Digibee API metrics with Datadog](/documentation/developer-guide/development-cycle/dashboards/pipeline-metrics/pipeline-metrics-api/how-to-set-up-digibee-api-metrics-with-datadog.md)
* [Highly scalable ETL model for Digibee](/documentation/resources/best-practices/highly-scalable-etl-model-for-digibee.md)
* [Pipeline version history](broken://spaces/jvO5S91EQURCEhbZOuuZ/pages/PkMz16oFtXSARL6zUehX)

## **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](/documentation/developer-guide/development-cycle/build-overview/canvas/ai-assistant.md) 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digibee.com/documentation/release-notes/july-2025/july-29.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.