CREATE & UPDATE events fired when issues is created in Workfront | Community
Skip to main content
tibormolnar
tibormolnar
Level 4
March 30, 2025
Solved

CREATE & UPDATE events fired when issues is created in Workfront

  • March 30, 2025
  • 3 replies
  • 700 views

Hi All,

I'm calling for Black Belt Fusion experts, hoping for help with resolving this mystery.

 

I have a custom form (with loads of fields) on the Issue object in WF. I have a Fusion Scenario that I need to run when one of these fields (FIELD2) is updated on an existing issue, or a new issue is created with this field populated.

The filters defined for the webhook look like this:

Record type: Issue State: New state Filters: DE:FIELD1 EQUAL Yes AND DE:FIELD2 Changed AND connection updates included Record Origin: New and Updated Records

 When I CREATE a new issue that matches the filters, 2 events are fired: one "CREATE" and one "UPDATE" event. So my scenario runs twice and I can't figure out why.

The Fusion scenario does not update FIELD2, so the 2nd event is not triggered by Fusion itself.

 

I checked the data in the output bundle of the "Watch event" Fusion module in both runs and found the following:

- The "newState" data is exactly the same in the CREATE event and in the UPDATE event (and it includes the custom field data).

- There are 2 differences between "oldState" and "newState" in the UPDATE event:

  - oldState doesn't include the custom form fields (only newState does).

  - in oldState the fields rootGroupID and groupID are null, in newState they have a value.

 

I don't understand why I have 2 events, I would only expect 1 CREATE event, since that's when FIELD2 is set.

 

I appreciate any advice.

Tibor

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 tibormolnar

Hi All,

I didn't pursue the workaround that @sven-ix suggested (i.e. filtering based on rootGroupID), because I have read that v.2. of the Event Subcription API fixes a behaviour which is very similar to mine:

Source of the screenshot:

https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/event-subscriptions/event-subs-versioning

I have updated both the CREATE and UPDATE event subscription behind my scenario to v.2. of the API and it solved the issue (even though the CREATE event triggering my scenario does not involve the use of a Template). Creating a record no longer fires 2 events, only 1 (CREATE) event is fired.

 

For instructions on how to update your subscriptions to v.2 (and on deadlines for doing this), refer to the above link.

Tibor

3 replies

Sven-iX
Community Advisor
Sven-iXCommunity Advisor
Community Advisor
March 31, 2025

I remember beating my head against the wall with this. Really annoying to have to filter out because on rootGroupID...

Do you need to know it was a CREATE event? 

    tibormolnar
    tibormolnarAuthor
    Level 4
    April 1, 2025

    Hi Sven,

    I need the scenario to run (once) when FIELD2 is updated on an existing issue, or a new issue is created with this field populated. In other words: I need the scenario not to run twice when a new issue is created.

    So, I guess, as a first step I'd like to understand exactly why this is happening. Did you manage to figure it out?

    Why is there an UPDATE event (too) when I create an Issue? What is rootGroupID?

    Thanks for sharing your knowledge!

    Sven-iX
    Community Advisor
    Sven-iXCommunity Advisor
    Community Advisor
    April 1, 2025

    I didn't manage to solve it. No idea why that's happening. I ended up using filters too. 
    You could also try 2 scenarios with a single event handler (one for new, on for updated only) and then use HTTP module to send the newState/oldState to a worker scenario. 

    Sorry i can't be of more help!

    Lawson02
    Lawson02
    Level 6
    April 17, 2025

    I've had this issue before and the only way I've would to fix it is to add an exists statement, but this assumes you only care when it exists and you don't need to know when its blank. Assuming the 2 statements is correct you could even try changing record origin to Updated records only.

    DE:FIELD2 Exists

    AND DE:FIELD2 Changed

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      July 16, 2025

      @tibormolnar Just checking in — were you able to resolve your issue?
      We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

      Kautuk Sahni
      tibormolnar
      tibormolnarAuthorAccepted solution
      Level 4
      July 18, 2025

      Hi All,

      I didn't pursue the workaround that @sven-ix suggested (i.e. filtering based on rootGroupID), because I have read that v.2. of the Event Subcription API fixes a behaviour which is very similar to mine:

      Source of the screenshot:

      https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/event-subscriptions/event-subs-versioning

      I have updated both the CREATE and UPDATE event subscription behind my scenario to v.2. of the API and it solved the issue (even though the CREATE event triggering my scenario does not involve the use of a Template). Creating a record no longer fires 2 events, only 1 (CREATE) event is fired.

       

      For instructions on how to update your subscriptions to v.2 (and on deadlines for doing this), refer to the above link.

      Tibor

        Terms & ConditionsAccessibility statement

        Loading footer...