Adobe Workfront Fusion: Watch event going into loop | Community
Skip to main content
lgaertner
lgaertner
Level 9
June 8, 2023
Solved

Adobe Workfront Fusion: Watch event going into loop

  • June 8, 2023
  • 1 reply
  • 872 views

Hello,

 

We are quite new with our Fusion instance.

 

I would like to create a simple scenario:

Using a Watch event on a custom field, an event should be triggered.

Before having access to Fusion I did that using the Event subscription API, which worked perfectly well.

 

Now I want to do the same in Fusion. I added a Watch Event and an Update Record module into my example scenario.

As soon as I change the field value to "Yes", the event is triggered, to update the record (just put the current date into another custom field), but it is called like every milisecond, until I manually deactivate the scenario. It seems to run into a loop.

 

If I list my event subscriptions via API, I cannot find out any difference between the entry created by Fusion and the one I created manually using the API.

 

Can you please help me?

Thanks in advance.


Regards
Lars

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ChrisStephens

The easiest way is to include the "exclude connection updates" parameter when you build your webhook.

 

Currently, this is what is happening, I'm guessing based on your description.

 

  1. You manually make an edit in Workfront to trigger the webhook
  2. The webhook sends the update to Fusion
  3. The fusion scenario starts
  4. The fusion scenario updates your custom field with (now) (which is date/time)
  5. Fusion's update triggers the webhook
  6. The fusion scenario starts
  7. The fusion scenario updates your custom field with (now) (new date/time)
  8. repeat steps 5 - 7 forever

This can be prevented by excluding the fusion user from triggering the webhook

1 reply

ChrisStephens
Community Advisor
ChrisStephensCommunity AdvisorAccepted solution
Community Advisor
June 8, 2023

The easiest way is to include the "exclude connection updates" parameter when you build your webhook.

 

Currently, this is what is happening, I'm guessing based on your description.

 

  1. You manually make an edit in Workfront to trigger the webhook
  2. The webhook sends the update to Fusion
  3. The fusion scenario starts
  4. The fusion scenario updates your custom field with (now) (which is date/time)
  5. Fusion's update triggers the webhook
  6. The fusion scenario starts
  7. The fusion scenario updates your custom field with (now) (new date/time)
  8. repeat steps 5 - 7 forever

This can be prevented by excluding the fusion user from triggering the webhook

    Terms & ConditionsAccessibility statement

    Loading footer...