copied from github issue:
See the above github issue for more details. The gist of it is, the readItem() or processItem() method throws a skippable exception that are configured to set transaction status to be rollback-only in other part of the application. The expectation is to skip the current item that caused this skippable exception, and also rollback the transaction associated with the current chunk. The next data item should start anew without being influenced by the previous chunk containing the skipped item.