I have two “Page is loaded” workflows running on the same page.
Each has a different purpose.
- Here is the first “Page is loaded” workflow. The action triggers a custom navigation sequence. It’s important to note that the custom navigation sequence doesn’t create anything in the database.
- Here is the second “Page is loaded” workflow. It should only run when the URL has a param of “oa_connector=direct_connection”. The action creates a new “Twitter Auth” thing in the database.
The problem is that I am seeing double entries in the database for the “Twitter Auth” thing.
To debug the problem I stepped through the app to see when the double entry is made.
It seems that the first “Page is loaded” workflow is ALSO creating a “Twitter Auth” entry in the database. But I never told it to do that.
I only told the second “Page is loaded” workflow to do that, so why does the first workflow create an entry?
And what’s the best way to stop this from happening? I cannot add the opposite condition of “only when oa_connector param is empty” to the first workflow because that would break my navigation. I still want the first workflow one to run if that param exists, I just don’t want it creating a Twitter Auth entry in the database (because I never told it too!).