Commit offsets action in the Kafka package
- Updated: 2026/05/15
Commit offsets action in the Kafka package
The Commit offsets action in the Kafka package enables you to explicitly commit a consumer offset for a specified topic, consumer group, partition, and offset value, confirming that the message at that position has been successfully processed in your automation workflow.
Prerequisites
- An active Kafka session established using the Connect action in the automation. See Connect action in the Kafka package.
- A prior Consume message action configured with the Manual commit strategy. The Commit offsets action is only meaningful when the consumer manages offsets manually. See Consume messages action in the Kafka package.
- The topic name, consumer group ID, partition number, and offset value are available — typically extracted from the output of the Consume message action. See Consume messages action in the Kafka package.
Settings
Use the Commit offsets action to mark a specific message as successfully processed by committing its offset to the Kafka broker. This action is used in conjunction with the Consume message action when the commit strategy is set to Manual. Committing an offset indicates to the broker that the consumer has processed all messages up to and including that offset in the given partition, so that the consumer resumes from the correct position on the next poll. The Commit offsets action returns a boolean value indicating whether the commit was successful.
- Session name: Select one of the following options to
specify the Kafka session to be used:
- Session name: Select the active Kafka session returned by the Connect action, or accept the default session name Default.
- Variable: Select a session variable that includes the active Kafka session configuration.
- Topic: Enter the name of the Kafka topic for which you are committing the offset. This must match the topic used in the corresponding Consume message action.
- Consumer group ID: Enter the consumer group identifier used to track consumed offsets. All automations sharing the same group ID share partition assignments and offset state. For example, erp-sync-group.
- Partition: Enter a non-negative integer (0 or greater) representing the partition number. This value is typically extracted from the table output of the Consume message action. For example, 0.
- Offset: Enter a non-negative integer representing the offset of the message to commit. The offset needs to set as N+1 and committing offset indicates to the broker that all messages up to and including offset N have been processed. This value is typically extracted from the table output of the Consume message action. For example, 142.
- Assign output to a variable: Specify the variable where the Commit offsets action stores the result. The Commit offsets action returns a boolean value. A value of true confirms that the broker has recorded the consumer's position for the specified topic, consumer group, and partition, ensuring that the next poll resumes from the correct offset. Use this variable in downstream steps to implement error handling or conditional branching.