Connect to next scenario dynamically using JSON

Features
,
1

Just an hour ago this was working:
Had one scenario call another scenario. Had set up API token in profile and plugged that in.
As you can see from the image (pls see image below):
Step 1 worked fine.
Step 2, though… after navigating to the correct scenario: It plugs in the scenario ID number and then stops there with a 404 error.
Since this worked before, I’m guessing this may be some issue with the Make network?
I noticed some other oddities today where modules that had never had issues in the past suddenly ran slow or errored-out.
Is this going to be an ongoing problem with Make?
Seeking ideas/help. Thanks!
Please see image.

2024-09-17-connect-to-next-scenario
2024-09-17-connect-to-next-scenario786×812 47.2 KB

3

OK I found out the issue but not a fix.
First: I had to delete the connection completely and create a new one.
Then it would allow me to choose a scenario and fill in some of the variables to send to the next scenario. Yay.
BUT here’s where it goes bad:
I want to fill in the Scenario ID dynamically.
So I highlight the scenario ID number it put in for me and - hoping to replace that number with a field results from previous module, as soon as I do that, instead of deleting that scenario ID and replacing with the dynamic field I picked, It puts the dynamic field beside the number, then goes to that 404 Not found error you saw in my image. So I refreshed the page and tried just deleting the scenario ID number in that input box, hoping I could then choose my dynamic field. Unfortunately, the second I delete that scenario ID, it gives that error. Help?

4

So. I decided to export the scenario to JSON and edit it that way to see if I can then import that JSON and that pesky connect module will work. First, though, looking at the JSON, I’m in need of advice. Here is the relevant part of the script:

 {
            "id": 234,
            "module": "make:runScenarioWithInputs",
            "version": 1,
            "parameters": {
                "__IMTCONN__": 3462685
            },
            "mapper": {
                "scenario": "3098234",
                "data": {
                    "id_session": "{{154.id_session}}",
                    "id_campaign": "{{155.`1`}}",
                    "id_client": "{{155.`2`}}"
                }

Calling your attention to the line with scenario, I changed it to be:

"scenario": "{{155.id_scenario}}",

and then imported the modified scenario JSON. It worked!
To Make devs:
“This is not ideal that users like me have to do this work-around. Please fix the connection module to more gracefully work as needed. Thank you!”

1 Like