> For the complete documentation index, see [llms.txt](https://docs.omnata.com/omnata-product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/contentful/release-history.md).

# Release History

***

### V1.22

#### Created: 2026-05-20

* Improved reliability of the ID lookup when response size of a single object is too big

***

### V1.21

#### Created: 2026-05-20

* Improved error handling

***

### V1.20

#### Created: 2026-05-20

* Fixed an issue where the ID-based error messages were not thrown

***

### V1.19

#### Created: 2026-05-19

* Fixed an issue where certain timestamp formats returned by the Contentful API could not be parsed
* When the "Response size too big" error is thrown on a page size of 1, an attempt will be made to fetch the record ID to include in the error message

***

### V1.18

#### Created: 2026-05-19

* When using a CMA token for inbound syncing, spaces which have been archived will now be automatically skipped

***

### V1.17

#### Created: 2026-05-19

* Added the space and environment context to error messages, where possible

***

### V1.16

#### Created: 2026-05-14

* Fixed an issue where consumer UDTFs did not work after the previous release
* Removed python dependencies already covered in plugin runtime

***

### V1.15

#### Created: 2026-01-20

* Fixed a bug introduced in the previous release, where the plugin fails to provide new records for some streams

***

### V1.14

#### Created: 2026-01-14

* Added a workaround for API payloads exceeding the 7MB limit

***

### V1.13

#### Created: 2025-12-02

* Add entries\_published and assets\_published streams for Content Management API

***

### V1.12

#### Created: 2025-11-11

* Adopted the synthetic primary key approach for all streams

***

### V1.11

#### Created: 2025-11-10

* Assets and Entries will now use a synthetic primary key which is a combination of the space id, environment id and asset/entry id

***

### V1.10

#### Created: 2025-11-06

* Fixed a pagination bug

***

### V1.9

#### Created: 2025-11-05

* Added extra debug logging

***

### V1.8

#### Created: 2025-10-20

* Added a consumer UDF for fetching Environments

***

### V1.7

#### Created: 2025-10-13

* When using CMA tokens, each environment within a space will be fetched and evaluated

***

### V1.6

#### Created: 2024-12-16

* Added more parameter checks to the consumer UDFs

***

### V1.5

#### Created: 2024-12-12

* Created three initial consumer UDFs

***

### V1.4

#### Created: 2024-12-05

* Improved error handling when fetching inbound stream items

***

### V1.3

#### Created: 2024-11-28

* Fixed an issue where sync configuration forms would error when using Content Delivery API credentials

***

### V1.2

#### Created: 2024-11-27

* Updated the plugin runtime to the latest version

***

### V1.1

#### Created: 2024-04-02

* Bump plugin runtime version
* Built with omnata-plugin-devkit==0.3.17 which includes pinned stored proc dependencies

***

### V1.0

#### Created: 2024-03-08

Switched to new plugin-oriented billing mechanism

***


---

# 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 dynamically by asking a question.

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

```
GET https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/contentful/release-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.