Hi Asheesh,
We faced similar issue recently in production. Literally everything is fine as mentioned by you. But finally the issue was because batch user WF-BATCH had some authorizations missing and this was the reason.
May be you can check your batch user authorizations as well.
Regards,
Madhu.
