Just fyi - I am using the Live versions and not /version-test/… All actions in a single workflow creates and updates things in the live site except for the DATA API plugin - that gets created in the version-test version.
I mean that your workflow request to data API may point to version-test endpoint and this may explain why whrn you test in live, the request to Data API is done to version-test DB. I guess this use thr API Connector. Check on this side.
Hi, This is using the Data API created by @copilot as below. It should automatically create in version-test when the version-test workflow endpoint is called and in live if the live endpoint is called:
@copilot - I know you mentioned that you do not offer support over the forums however I have not received any feedback via email. Any feedback/update on this issue will be much appreciated. If you can maybe assist with an interim workaround also I would appreciate!
Hello. I have the exact same problem. Did you ever hear back or figure it out? I tried creating a different token for live vs. test but that still did not work…
Thanks!
Instead of writing separate workflows for test and live versions, you can use bubbles “App version” option, “version-App version”. See screenshot below.
The weird thing is that I’m seeing the same base URL for the Data API, when I go to live mode or to test mode.
This shouldn’t happen because the POST request to data API to create a new thing is creating it in test mode, so when app I run in production, it’s not able to access the data.