Why does Stripe cancellation date still show after reactivating a subscription in my Zap?

Hi @Jakob.25 

For us to have more info, post screenshots to give us context about where you are referring to that data point.

• Is it in the Zap Editor?
• Is it in the Zap Runs?

Hi @Troy Tessalone,

the Zap runs fine. I see the wrong information in my zap history.

The zap run shows: “cancel_at_period_end: false” which is correct

on the other hand it shows at a different point the old cancellation date: Attribute: “KUENDIGUNGSDATUM:

{{263128979__cancel_at}}” which is not current anymore.Stripe didn´t overwrite the information I guess.

@Jakob.25 

For us to have true context about what you are referring to include screenshots.

For us to have more info, post screenshots to give us context about where you are referring to that data point.

• Is it in the Zap Editor?
• Is it in the Zap Runs?

Here you see that the stripe data out info says that the plan isn´t canceled. But the Brevo Data in info still shows the cancellation date from the past plan.
I hope the screenshots help.

@Jakob.25 

You may need to remap a variable between Zap steps.

These are different variable:

• cancel_at_period_end
• cancel_at

I know that these are different variables. Just wanted to showcase that the stripe data is contradictional.

The  problem is in this attribute:

When a subscription is active, this attribute should get an update. Thats how the Zap should act. All the other datapints got updated. I was expecting that the field would be empty (or no data) because there is no current cancelation date.

@Jakob.25 

If a variable value is blank/empty/missing/null, then it won’t update an existing value to be removed.

Some apps provide specific values to use to remove an existing field value.

Otherwise, it can involve using the app API to clear out an existing field value.