ian11
1
I’m sharing this for the benefit of the community since I just wasted two hours of my life trying to figure out what was happening…
This involves stripe Subscriptions.
My App has a data base item for the subscription, and then it creates a subscription in stripe and synchronizes the info.
In my app, there are two ways to make a Stripe subscription…
#1 - Created by the app. Data base item is created and pushed to stripe.
#2 - Created by an outside app. In this case my app listens for the stripe subscription to be created and then creates the database item.
To prevent duplicating subscriptions I have a condition on the inbound webhook workflow “if this (Database) Subscription exists, terminate this flow”
Now we get to the confusion…
In my hot fix environment I was experimenting with subscriptions…
And it was creating duplicate subscriptions for some odd reason.
Here’s what was happening…
- I create a subscription in my app…
- The app pushes the information to Stripe, which creates a subscription and fires back a webhook with the subscription info
- My Hotfix environment doesn’t get the message, it’s not even hooked up to stripe
- My development environment DOES get the message and since there is no subscription item (different environment) dutifully creates the subscription item in my database…
- Here comes the weird…
- The hotfix and development environment synchronize with each other… and now it looks like there are two subscriptions created.
Anyway - TLDR: Hotfix and Development databases synchronize and this can be confusing sometimes.
Firstly, Why are you experimenting with a hotfix? LOL
Second, There are only 2 DB’s, Prod and Dev. So there is no new Database when you create a hotfix.
1 Like
ian11
3
Ha - Great question.
The answer is because I urgently needed to make a change, but I had to test it of course.
And I wish I knew there were only two environments… would have made my life a lot easier 
1 Like
ian11
4
I urgently needed to make a change and my dev environment is a disaster because I am working on a major update