[Custom App] Make is mixing up envs while developing new version

Questions
1

:bullseye: What is your goal?

Developing a new version of my custom app

:thinking: What is the problem & what have you tried?

I’m developing a new version of my custom app.

While testing, we switched all the URLs to Debug environment, so we can test it with our Debug backend new functions.

The custom app is working great until I publish the scenario and test it with “real data”: when some data triggers my scenario we hit a 401 error because Make is trying to call the /login endpoint on Production environment, not the Debug one.

Also, if we “Run once” with old data, the scenario works fine.

:clipboard: Error messages or input/output bundles

Failed to verify connection ‘Debug Connection Name’. Status Code Error: 401

3

Hey @247X_Dev,

Unless a question is about syntax, helping out with Custom App related problems is virtually impossible for community members. We just cannot resolve it without full access to the codebase and even then Make’s App engine has some quirks.

You can open a ticket with the Customer Care team. The official Make support has access to internal systems and logs, and can help you with technical issues, bugs, and all other questions regarding Make.

When you get the issue resolved, feel free to post it in the community to contribute to the knowledge base.

Thank you :folded_hands:

Cheers,
Henk

4

Hey Henk, thanks for your reply.

I already opened a ticket, but I was wondering if:

  • I was missing something to change while developing the new version (already changed in Base, Connections and Webhooks)
  • Is it possible that Make has some cache or something with login/account behavior

Thanks anyway.

5

Was the Custom App reviewed and published already of is this still in dev setup?

I’ve ran into a similar problem before, a long time ago (but never since then). At the time, it seemed like some earlier state was cached and I was not working with the most recent published app. I mitigated that by building as much of the app as possible and then building a scenario from scratch to test it. Also building a new connection, as I think connection state persists from the moment it is created.

Never found a definitive answer though, so it is just conjecture.

Cheers,
Henk

6

The Custom App is reviewed and published, but I’m working on a new version of it.

So the new version is in debug still, but the current one is published.

I also tried creating a new scenario with a new connection, because I was thinking the same about some data persisting for connections, but still getting this problem.

Hope they can help me through the ticket.

Thanks again for your reply.

7

Hello, this is the reply we got from the support, we just ask if there’s some workaround to also test triggers. After that I’ll close the thread.

1. If scenario is run once, manually, it’s using the newest version of the code.
2. Scheduled runs while having uncommitted changes (as your app does), will trigger the Published approved version of the app.

Above means that it won’t be possible to be tested through the scheduled runs.

Next steps

​1. Finish testing through the “Run Once”
2. Submit changes to the review for our team.
3. Once it’s released, you can validate your changes through the scheduled runs in the prod version.

Sorry for the inconvenience caused, that’s specifics of the platform.

8

Thanks for sharing, makes sense because this is a reviewed and published app!

12

Hi everyone, I just received the reply from the support.

So, if you have a published app and you’re updating it using a debug API URL, you can’t test your scenarios using triggers (scheduled runs) but only with “Run Once”.

Hope they change this behavior because “going live” is not the best way to test stuff :smiley:

​Best way unfortunately with the limitation is to use “Run Once”.

I do see your app changes are requested, will be released tomorrow and you can validate with the scheduled runs. Sorry about that inconvenience.

Thanks for the support,
have a nice day!