krileon wrote: Strange, you must have something else triggering a user store or something interrupting the reversal. Are you using CB Auto Actions? If so try disabling it and see if issue persists.

I use auto-action but for different action than this one. I try with auto-actino disable but same results

krileon wrote: Do you have CBSubs SQL Actions updating the field with a database query? If so remove the query.

I have CBsubs SQL actions but not one this field. This field was create for testing so there's no action on it..

krileon wrote: Below is process showing it working fine with a text field (what you should be experiencing with your text field)

Here are my screenshot :
CBSubs Field Configuration:



Plan After Subscribe:


Field After Subscribe:


Plan After Unsubscribe:


Field After Unsubscribe:

krileon wrote: If editing the subscription within CBSubs > Subscriptions it will not fire any triggers for integrations to function. Same for database edits. It must expire naturally or be unsubscribed from frontend or in backend user management.

Ok I learn something, I was doing wrong by editing within CBSubs > Subscriptions. It doesn't change for this problem but it's good to know, thx.

I've test once again this morning :

- with auto-action unpublish, same result
- with CBSubs SQL actions unpublish, same result

I don't know what to do to solve this problem... When you told me that the process you describe was working fine, do you have made some test with several CBSubs Field on the same plan ?

krileon wrote: Please describe how you're testing for it to be working. You need to be subscribing on frontend through the dummy gateway for example. Then afterwards go to your profile and unsubscribe. That's the test flow I was doing. Please let me know exact steps how you're testing.

It will be more easier for you to understand with this : video for test

ok Kyle, I have understood what you mean and from now I will say to my customers that the right process to unsubcribe a member is on the front. I've made the test with frontend unsubscribe ( see the video here ) to show you that it doesn't change anything, the field stay on Valid.

For the case we were speaking about in the beginning the problem was when the subscribe time was over, that was the reason why I was unscribing from backend.