All I can tell you is the the post job is firing but the record is not committed to table that called the post job in the first place. Would not an exception thrown in the post job make the post fail? The exception is coming from the S3 service as explained above for duplicate folder (which should not be an exception).
edit PS. If the S3 service didn't throw exceptions for existing folders, I would consider this my issue to solve and not a bug. But since the post to the db worked fine without the S3 bit, I have to assume the exception from S3 is the cause of the failed commit to the db.
