Hi. I have two scenarios that are designed for a different workflows. Both are meant to be triggered when Adobe Sign document is signed.
Problem I’m having is. Workflow 1 is run it gets executed properly. I get an error in Workflow 2.
I checked AirTable and Adobe Sign and the webhooks are where they meant to be and are not used in that different workflow/scenarios.
Anyone ever came across similar issue? And if so, where should I start looking in?
Are you getting error messages? If so, what do they say? Look at the execution history of the scenario that fails. It should give an indication of the problem.
L
Hi. Thanks for responding. The problem is that I get an error in a scenario that should not have run since it’s triggered from another scenario which is not linked to the scenario that gets the error. It’s always in the last module as shown on the screenshot but the previous modules should not have run at all.
So it looks like an external process (or another scenario) may be calling this one. Without understanding your tech stack, it’s hard to know where the problem is.
If you deactivate that scenario and run Adobe Sign, what happens? I suspect that whatever external process is calling this one does not have the correct “IF” statement to prevent it being called. So the problem may not be with make but with the Adobe Sign trigger.
L
Hi. Thank you for that insight I think you are right that’s not so much related to make but to outside party I just can’t figure out what party (adobe or airtable) and can’t get that troubleshoot properly.
Do you control how the data is sent to Make? If so, you could add a field in the webhook call that identifies the caller and anything else that can help you identify who is calling the webhook.
Another option is to clone your scenarios and use one for Adobe and the other for Airtable until you can debug the problem. The disadvantage is that you need to update two scenarios when you make a change. Of course, you can just do it temporarily and delete the clone afterwards.
L
Hi. Thank you for your suggestion. I’ve never done something with adding a field in the webhook so I’ll need to investigate that.
In the meantime we reach out to Adobe for some input as I think the issue is on that side of the webhook and we hope to get some clarity there as we just started another webhook in the account and I think we might not have set it up properly.
