Hi Kyle,
I think you misunderstood me, I wasn't saying that CBSubs was erroring, I meant it showed an error in the history log. As to the date format, as per above, that was fixed long ago & is being submitted correctly for the activation & renewal so why is it not working for the expiration? the exact same information is being sent (same on the activation, renewal, deactivation & expiration). also when I test it via the URL (not cbsubs, i mean the literal URL in the browser) it works perfectly. So somehow CBSubs is submitting the information incorreclty and I cannot figure out why or what it is. If it is submitting the expiry date based on the CB config like the activation & renewal, that would be correct. But again, the expiration seems to be doing something differently & it shouldn't. Please see images & the private message I sent you that contains the URL I used for testing.
So this will most likely require troubleshooting to see why CBSubs is sending different information when it should be the same
We need a way to see the information that is being sent from CBSubs so we can see what the difference is from activation/renewal to the expiration post. Then we can alter the format accordingly, but without seeing the post information being sent I cannot confirm what is causing it. Please advise, thank you