Notifications
Clear all
Topic starter
Hello. I have two workflows set up for different processes. Both are intended to activate upon the signing of an Adobe Sign document.
The issue I'm encountering is that Workflow 1 runs and executes correctly, but I receive an error in Workflow 2.
I've verified that the webhooks in Airtable and Adobe Sign are correctly configured and are not being utilized by the other workflow/scenarios.
Has anyone experienced a similar problem? If so, where would be a good place to start investigating?
Posted : 03/01/2025 4:30 pm
Are you encountering any error messages? If so, what do they state? Examine the execution history for the scenario that is failing. This should offer a clue to the issue.
Posted : 04/01/2025 4:50 am
Topic starter
Hello. Thank you for your response. The issue is that I'm encountering an error in a scenario that shouldn't have executed, as it's triggered by a different scenario that isn't linked to the one producing the error. The error consistently appears in the last module, as indicated in the screenshot, but the preceding modules should not have run at all.
Posted : 04/01/2025 8:21 pm
It appears an external process or another scenario might be invoking this one. Without insight into your technical setup, pinpointing the exact source of the issue is challenging.
Could you try deactivating that scenario and then running Adobe Sign? My suspicion is that the external process initiating this one lacks the appropriate "IF" condition to prevent unintended calls. Therefore, the issue might stem from the Adobe Sign trigger rather than callin.io.
Posted : 05/01/2025 4:26 am
Topic starter
Hi. Thank you for that insight, I believe you're correct that it's not so much related to callin.io but to an outside party. I just can't figure out which party (Adobe or Airtable) and can't troubleshoot it properly.
Posted : 06/01/2025 5:09 pm
Can you manage the data transmission to callin.io? If that's the case, you might consider including a field within the webhook request to specify the caller and any other details that would help identify the source of the webhook call.
Alternatively, you could duplicate your scenarios. Use one for Adobe and another for Airtable while you work through the issue. The downside here is that you'll need to maintain two scenarios whenever an update is required. Naturally, this could be a temporary measure, and you can remove the duplicate later.
L
Posted : 06/01/2025 7:41 pm
Topic starter
Hi there. Thanks for the suggestion! I haven't previously worked with adding a field to a webhook, so I'll need to look into that.
In the meantime, we've contacted Adobe for some input, as I suspect the issue lies on their end with the webhook. We're hoping to get some clarification, especially since we just set up another webhook in the account and might not have configured it correctly.
Posted : 07/01/2025 2:55 pm