# Release History

***

### V1.18

#### Created: 2026-05-28

* Added apple\_pay object to transactions schema

***

### V1.17

#### Created: 2026-05-25

* Fixed an issue where full refresh syncs did not disregard stream state

***

### V1.16

#### Created: 2026-05-25

* Added credit\_card.debit and credit\_card.issuing\_bank to transactions schema

***

### V1.15

#### Created: 2026-05-21

* Reverted status\_history to an array type in the JSON schema

***

### V1.14

#### Created: 2026-05-19

* Fixed some JSON schema properties in the transaction stream
* Added FETCH\_CUSTOMERS UDTF for ad-hoc customer batch fetching by ID

***

### V1.13

#### Created: 2026-05-15

* Fixed an issue where custom\_field values appear as empty strings, breaking the normalized views

***

### V1.12

#### Created: 2026-05-15

* Instead of fetching all identifiers first, we now fetch them in alternate operations so that checkpointing is more effective

***

### V1.11

#### Created: 2026-05-13

* Fixed an issue where the plugin would not respond to cancellation requests within an active stream

***

### V1.10

#### Created: 2026-05-11

* Removed nested subscriptions from customer payment methods

***

### V1.9

#### Created: 2026-05-04

* Expand stream schemas to expose all Braintree REST fields in normalized view
* Fixed an issue where timezone mismatch caused an error
* Fixed an issue where records could be missing from the stream
* Fixed an issue where memory was not being freed up after a batch of records was processed

***

### V1.8

#### Created: 2026-05-01

Fix memory exhaustion on large REST syncs by batching enqueue calls Merge pull request #10 from omnata-labs/fix/rest-memory-exhaustion Fix: Memory exhaustion on large REST syncs Merge pull request #11 from omnata-labs/fix/schema-field-coverage Expand stream schemas to expose all Braintree REST fields in normaliz…

* Fixed an issue where timezone mismatch caused an error
* Improved memory management
* Fixed an issue where records could be missing from the stream

***

### V1.7

#### Created: 2026-04-28

Fix memory exhaustion on large REST syncs by batching enqueue calls Merge pull request #10 from omnata-labs/fix/rest-memory-exhaustion Fix: Memory exhaustion on large REST syncs Merge pull request #11 from omnata-labs/fix/schema-field-coverage Expand stream schemas to expose all Braintree REST fields in normaliz…

***

### V1.6

#### Created: 2026-04-28

Memory Fix and Expand Streams Fields

***

### V1.5

#### Created: 2026-02-26

* Switched to REST API for transactions and subscriptions
* Now using id search plus parallel batch fetching

***

### V1.4

#### Created: 2026-02-23

* Introduced parallel processing of streams

***

### V1.3

#### Created: 2026-02-18

use graphql, and fix subscription 10k cap and incremental sync (#5)

* Switched to the graphql API for transactions, customers, and dispute
* Fixed an issue where the subscriptions inbound stream could miss data

***

### V1.2

#### Created: 2026-02-12

* Added more fields to transaction stream

***

### V1.1

#### Created: 2026-02-06

* Fixed an issue where a single stream error may disrupt a whole sync run

***

### V1.0

#### Created: 2026-01-15

* Initial release of plugin, supports inbound syncing of Transactions, Subscriptions, Disputes and Customers

***


---

# 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.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/paypal-braintree/release-history.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.