Are there any errors in the workflow execution logs? Please navigate to Admin → Workflow Automator and open the affected workflow → Click on ‘Execution Logs’ on the top right. The API call-back URL, payload passes and response received will be shown there. This should help you identify and resolve the issue better.
If the issue persists, please help us with the name of the workflow and the affected ticket IDs so we can ask our support team to troubleshoot the issue further.
Are there any errors in the workflow execution logs? Please navigate to Admin → Workflow Automator and open the affected workflow → Click on ‘Execution Logs’ on the top right. The API call-back URL, payload passes and response received will be shown there. This should help you identify and resolve the issue better.
If the issue persists, please help us with the name of the workflow and the affected ticket IDs so we can ask our support team to troubleshoot the issue further.
First time I trigger my workflow automation - everything goes fine. (I load details of an associated asset in order tos et correct SLA based on the asset connected to a ticket).
If I a few minutes later trig the same workflow It just stops with the error “ Workflow is waiting for another event Web Request Response”
If I look at the request log - I can only see the first successful call - not the second one that fails (or at least does not continue running after web call.) The call is to Fresh API (hardcoded asset id 15 for test purposes: https://shibuya.freshservice.com/api/v2/assets/15?include=type_fields )
As you can see in activities - the second call just ends with waiting for another event Web Request Response. (Below you can see the result of the previous identical call which succeeeded,
Any Idea what I’m doing wrong?
In the log - I can only see the first successful call:
i think, you get no response because calls to the Freshservice API requires your API key, not your User & Password authentication. I dont know when you create your Account, is it after31-Aug-2021?
First i created a Reader (R2) using liquid + placehodlers to get the correct asset for my use case
then i created a Parser from Asset custom_field ({{R2.custom_fields}})
Previously I didn’t know that behind the scenes there are fields not selectable by placeholders that could be accessed using Readers and Parsers, but a wild guess turned out to be fruitful!