# GCPStorage sink plugin committed offsets

**URL:** <https://ask.lenses.io/t/gcpstorage-sink-plugin-committed-offsets/437>\
**Category:** General\
**Tags:** kafka-connect\
**Created:** [October 2, 2025, 9:54am UTC](https://ask.lenses.io/t/gcpstorage-sink-plugin-committed-offsets/437 "2025-10-02T09:54:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Umar\_Cheema](https://dub1.discourse-cdn.com/flex017/user_avatar/ask.lenses.io/umar_cheema/32/177_2.png) [@Umar\_Cheema](https://ask.lenses.io/u/Umar_Cheema)\
**Post date:** [October 2, 2025, 9:54am UTC](https://ask.lenses.io/t/gcpstorage-sink-plugin-committed-offsets/437/1 "2025-10-02T09:54:06Z")

</div>

We are using the GCP Storage Sink Connector with the following property set to false:

“connect.gcpstorage.exactly.once.enable”: “false”

In our test, we send 10 records, which are processed and written to a file. However, when we delete the connector configuration or job and then recreate the job, a new file is written starting from offset 9. Is the plugin reporting the committed offset as the actual offset minus 1?