Failed to Register Watcher

Wasdom_Kung
Tera Guru

Hello,

I have a flow that was working a short while ago that seems to be throwing the following error:

 

Failed to register Record watcher for ee913757d69f12109edb436d6922ee98 with condition sys_id=5b917757c39f121015807e43e401314e on table sysevent

 

Wasdom_Kung_0-1738231853482.png

The flow uses a wait condition, that will only progress the flow when an inbound action detects 'approved' in parm2, and the subject contains approved and the watermark is present in the body of the email response - however, after the email is returned, it is shown on the RITM activity feed but the action is still sat in "waiting" state, despite the criteria required matching.

 

Does anyone know how to fix this, or what is causing it?

 

Edit: I've noticed on other parts of the flow the watcher isn't initialised either, such as during an if condition:

Wasdom_Kung_0-1738232369152.png

 

 

Edit 2: I think the record watcher is a red herring - I checked the inbound email response, and the inbound action is executing but won't update the record despite meeting the requirements:

Wasdom_Kung_0-1738234099132.png

 

 

1 ACCEPTED SOLUTION

Wasdom_Kung
Tera Guru

This issue magically resolved itself after adding a new action to the flow and saving it, it now works as it used to.

View solution in original post

4 REPLIES 4

Ankur Bawiskar
Tera Patron
Tera Patron

@Wasdom_Kung 

check this link

Flow Designer 'Wait For Condition' can encounter a race condition leaving the flow stalled in the wa...

Did you recently upgrade? Why it shows 14 days in Duration?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hi Ankur,

 

The 14 days condition turns true when the inbound action role detects a watermarked response containing approval in the body text of the email, when true, this condition then changes to complete and the task spawns.

Wasdom_Kung_0-1738252628375.png

Wasdom_Kung_2-1738252864307.png

I believe we upgraded a month or two ago, we are on Xanadu now, one of the later patches, below you can see the RITM was updated with the approval email:

Wasdom_Kung_1-1738252727156.png

 

Edit: Sysevent table is showing that the parm2 value is also correct and processed, but if a watcher is not initialising on this table, then it'll never know that it has worked, so I am back to thinking that this is the problem.

Wasdom_Kung_1-1738314117128.png

Ankur Bawiskar
Tera Patron
Tera Patron

@Wasdom_Kung 

seems your RITM didn't update and the update was not passed to flow and hence it's still waiting

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Wasdom_Kung
Tera Guru

This issue magically resolved itself after adding a new action to the flow and saving it, it now works as it used to.