> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/changelog/release-note/2025/q1-2025.md).

# Q1 2025

Release notes for January to March 2025.

{% updates format="full" %}
{% update date="2025-03-29" %}

## 0.5.2637

* Added `sendCredentialsAsFormParams` option to OAuth2 connection settings.
* Improved error message in layout vendor when vendor is unauthorized.
  {% endupdate %}

{% update date="2025-03-27" %}

## 0.5.2635

* Added `CheckForExistingPasstype` parameter (default `true`) for Pass Pipeline flow element.
  {% endupdate %}

{% update date="2025-03-17" %}

## 0.5.2610

* Fixed `notEquals` filter when field doesn't exist.
* Fixed push update task settings editor UI.
* Fixed issues editing Google pass editor config and SmartTap.
  {% endupdate %}

{% update date="2025-03-16" %}

## 0.5.2603

* Allowed pass layouts to retrieve pass ID from external identifier + HMAC-SHA256 (or secret).
* Reviewed date display to show date using the browser timezone.
  {% endupdate %}

{% update date="2025-03-12" %}

## 0.5.2592

* Added active count in pass stats API.
* Improved UX for scheduler log management.
* Technical improvements for multi-instance internal distributed cache.
  {% endupdate %}

{% update date="2025-03-06" %}

## 0.5.2585

* Added “not equals” operator in push update filters.
* Added UI to get task scheduler logs.
  {% endupdate %}

{% update date="2025-01-16" %}

## 0.5.2432

**Added**

* Added a Scheduler page.
* Added an Engage page (beta).

**Improved**

* Improved the SFMC configuration editor.
* Added support for default values on date fields (including `datePart` in datebox fields).
  {% endupdate %}

{% update date="2025-01-08" %}

## 0.5.2424

**Added**

* Added a **Last update date** column in the Passes list.
* Added a new back-office language.
* Added a **Need help** button below the QR code on the pass page.

**Improved**

* Allowed saving a pass type and sending a push update in the same flow.

**Fixed**

* Fixed localization and Google Wallet edge cases.

<figure><img src="https://2425106641-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FohFVLgeDoRJUI1NJz3Js%2Fuploads%2Fgit-blob-0961e53d640e3ce1eb3c2a5f5eef53e0b7d80ee1%2Fresources-release-note-pass-type-save-push-update.jpg?alt=media" alt="Pass type: save + push update"><figcaption><p>Save + push update a pass type.</p></figcaption></figure>

<figure><img src="https://2425106641-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FohFVLgeDoRJUI1NJz3Js%2Fuploads%2Fgit-blob-0961e53d640e3ce1eb3c2a5f5eef53e0b7d80ee1%2Fresources-release-note-pass-need-help-button%20(1).jpg?alt=media" alt="Pass page: need help button"><figcaption><p>Pass page: “Need help” button below the QR code.</p></figcaption></figure>
{% endupdate %}
{% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/changelog/release-note/2025/q1-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.