Currently the workflow uses the batch subscribe or unsubscribe to delete member tags, This operation is performed in chunks of 500 records per request. The current implementation will only catch the last request response errors which is not ideally in a situation where you have more than one chunk.
Improve the workflow to handle chunk response errors
See the implementation from the first workflow for inspiration
Summary,
Currently the workflow uses the batch subscribe or unsubscribe to delete member tags, This operation is performed in chunks of
500
records per request. The current implementation will only catch the last request response errors which is not ideally in a situation where you have more than one chunk.Improve the workflow to handle chunk response errors See the implementation from the first workflow for inspiration