I believe you cannot trigger a DID_CHANGE_RENEWAL_STATUS with a auto_renew_status of false multiple times in a row? According to the documentation if I understood correctly, DID_CHANGE_RENEWAL_STATUS receipts are triggered when a user indicates that they wish to stop their subscription under the subscriptions page in the app store itself. When a user presses the cancel subscription button, a DID_CHANGE_RENEWAL_STATUS with a auto_renew_status of false will be sent to me from Apple. The next time the user visits that page on the app store again, the only option they will have is to re-activate their subscription through 1 of our provided subscription plans and choosing any of those plans would then trigger a DID_CHANGE_RENEWAL_STATUS with a auto_renew_status of true.
I have received 4 DID_CHANGE_RENEWAL_STATUS with a auto_renew_status of false 4 times so far from the same unrecognised original_transaction_id. That does not sound possible according to my understanding.
We use server-to-server notifications from Apple in our subscriptions manage service. I can tell that DID_CHANGE_RENEWAL_STATUS works as expected for us. When user cancels subscription, we have auto_renew_status as false, and true when he enables it back.
I believe you are missing something. BTW why you need those notifications? They are almost useless.
This article may help you to understand how notifications work. Hope you find an issue in you code. You can also write us in online chat.