Need clarification on pending_change event

We’re receiving a pending\_change event from GitHub (markeplace app).

Currenlty, we’re only handling the changed event.

Dooes changed event always follow pending_change if the purchase/upgrade was successful?
Or do we need to handle pending_change the same way we handle changed (i.e. acknowledge the purchase/upgrade on our end)?

1 Like

Apologies for the long turnaround on this question …

@gylaz wrote:

Dooes changed event always follow pending_change if the purchase/upgrade was successful?

It should, but that’s not to say it always happens. If the change doesn’t get put into place, something went wrong on our end and the user would continue to receive whatever benefits were a part of the old plan.

Or do we need to handle pending_change the same way we handle changed (i.e. acknowledge the purchase/upgrade on our end)?

What you choose to do with the information a user has scheduled a change is up to you, but to indicate an upgrade has taken place might lead to confusion — the benefits of the new plan would not be made available until the change has been implemented and the changed event recorded.

Essentially, the pending_change event is there to give you extra information or context if you need it, but changed is when things really go into effect.

I hope that helps!

1 Like

Great, that explains what I was after. Thank you!

1 Like

I also just found “pending_change” actions in my logs. The docs also mention “pending_change_cancelled”, but neither is explained. Maybe ammend the docs to clarify what these actions mean?