Workflow with Trigger Webhook runs on 1 branch but not the other

Ask for Help
1

I have a workflow setup that runs on submission of a form. The workflow has two branches - for both branches, I want the Trigger Webhook function to run sending a JSON package to an external URL.

This works fine on the ‘else’ side (sending the JSON), but the Trigger Webhook action does not run if the conditions are met and ‘branch 1’ is executed - it is simply skipped while all other actions are running. I’ve tried adding a ‘wait for condition’ action as well ahead of it, but it does not change anything. All the data is available so that should not be stopping the action from running.

I’ve looked through the forum and exhausted the potential settings I can amend. Any idea for what I could do?

Thanks!

image
image650×478 29.5 KB

image
image587×488 20 KB

2

What happens if you replace the “Trigger webhook” action with a notification action, does this notification display correctly?

1 Like
3

Yes - there are already notification actions above the trigger webhooks, which on both branches display correctly. In the log file it shows that all other actions trigger correctly, except for the Trigger Webhook on the left-hand branch.

4

I see that you have 5 conditions in the wait just before the Trigger Webhook.
Are you confident that all 5 of them are being met?
What do you see in the workflow run log? Check the exit status of the wait.

3 Likes
5

I would add a notification between the conditional wait action and the webhook trigger: if the notification doesn’t display, then you probably have to troubleshoot the conditional wait action.

1 Like
6

Thanks for the suggestions! I’ve just tried running the workflow again and neither the notification nor the Trigger Webflow is present in the log.

image
image2393×531 52.4 KB

I’ve also tried removing the ‘wait for conditions’ action, as it was solely placed there to see if it could help trigger the Trigger Webflow action. This did not help as the Trigger Webflow did not run either.

image
image2278×437 49.5 KB

As a third option, I tried placing the Trigger Webflow at the beginning of the branch to see if the other actions would run. And yes, it skips right past the Trigger Webflow.

image
image2265×477 50.9 KB

And @Darren_Murphy, there is no exit status of the wait in the log as it also seemed to skip this action.

Could it be that the published site doesn’t update to reflect the workflow with a Trigger Webhook on both branches as it initially only had the Trigger Webhook on the ‘else’ branch?

7

Wait… are you testing this in the builder, or in the Published App?
If the published App, try this:

  • Make a minor change to the App layout
  • Publish the App
  • Re-test
2 Likes
8

That worked!

Super odd - so despite having auto-publish on, it does not publish changes when solely working in the workflow space.

But thanks for the help, now I can get it to work!

9

A secondary question:

image
image1303×523 50.3 KB

As you’ll see from the above workflow, I want to Trigger a Webhook that sends a JSON with the data from the original row in the data, which it does fine with the workflow above. But I also want to send a JSON with the new added row - adding a Trigger Webhook again after the ‘Add row’ action just sends the original row. How would I go about sending the new row that has been added as well?

10

You probably want something like the following:

  • Capture the RowID of the new row (from the Add row step), and write it to a User Specific column
  • Use that to build a single relation back to the table where the row was added
  • Use a lookup to grab the JSON
  • carry on from there..

Yes, it’s a known issue.
Making a small layout change is the current workaround.

1 Like
11

I do this sometimes when I rename an app and for some reason the name does not stick immediately in the dashboard.

Do you understand what’s going on?

12

I’ve seen that as well, and I don’t know what causes it. I can’t imagine it being related to the issue in this thread though.

1 Like