I am attempting to import a template (from someone else’s link) and when I click into the scenario, I am immediately shown an error (image attached).
The problem is, Make won’t allow me to click into any of the modules to update them to “fix” the error. Also note, in the image, no menu bar at the bottom, no option to save, etc. The “Skip guided setup” button also does nothing.
I should also state that I have been able to successfully load templates and convert them into scenarios and save them before. No idea why this is happening.
For complex technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Yes, I’m unable to edit the modules, and there are no guided setup prompts, and I’m unable to exit guided setup, and unable to create scenario using the bottom button either.
I just received a response from support and neither option they offered has worked.
Here is what they suggested:
Blockquote You see the error message because the scenario does not have any connection linked for the modules being used. You need to add new connections for all the modules and then run the scenario, it will work.
You can also, try the following solutions: 1. Open the scenario from the template. 2. Use keyboard shortcut ctrl+S(Windows) or CMD+S (Mac). 3. Now, come back to the Scenarios page, your newly created scenarios will be in the list. 4. You can open the scenario and edit it to add connections and use it. > Blockquote
Again, both did not work.
Another email response in to them just now, will keep you updated.
Some solutions, some theories and workarounds for what can’t be proven (YET).
Let’s start with solutions:
If you receive this error (as in first post), ask the template creator to send you a .json file of the scenario and import it.
Note: You will still need to create connections to apps in order to save the template as a scenario.
Hack/Workaround for having to create connections to save a scenario. I have found as long as the first module is connected (or doesn’t need a connection", you can simply unlink the rest of the modules right between the first module and the second. Which will allow you to save the scenario (with warnings/errors). Obviously, to run the scenario, you’ll need to add connections in at some point, but this is for if you have a time constraint and need a quick save of the template with connecting everything first.
Note: If the first module requires a connection for the template to be saved as a scenario, you have 2 options:
Connect it (and then unlink the rest as stated above in #2.
OR
Take note of what kind of action it is and what app it is and delete the module.
Now the theories:
Theory #1: The vendor had a Teams account, and downgraded their account, not knowing that this would disable their template sharing abilities for existing templates.
Theory #2: The vendor most likely didn’t know Theory #1 would happen
Theory #3 Make support seems highly uninterested in resolving and/or confirming what is going on here to cause such a cluster. Which means, you’ll probably be reading this and using the above solutions /workarounds until it is fixed/updated.
I asked Make support to confirm Theory #1 for me, to which they replied
I am sorry but I do not have access to that information as it is not possible to identify the information from the template links. Let me know should you have any further questions related to this issue. If you need help with something else, please submit a new ticket and we will get back to you promptly.
That’s all I have. I have my workarounds, I hope they help you in avoiding errors (at least until this is confirmed/fixed by Make.
