ATF getting cancelled at Click a UI Action

Henri Muldre
Tera Guru

Hi,

 

After upgrading our instance to Tokyo Patch 1, we have one Incident Task Resolution ATF, where the last step is:

  • Click a UI action: Confirm that browser submits 'Incident Task' form to server within 5 Seconds of clicking UI action 'Save'

The test keeps getting cancelled with message "This step did not execute due to the execution being canceled".

I tried increasing the "within 5 seconds" to 20 seconds, but still keeps getting cancelled?

I ran the same exact test with same exact steps on another similar instance with Rome patch 9b and it was a success there.

 

Any ideas?

1 ACCEPTED SOLUTION

Henri Muldre
Tera Guru

Update!

 

To anyone scratching their heads at this:

I heard back from ServiceNow NowSupport and they said that they were able to reproduce this issue in their OOB Tokyo instance. They created a problem ticket and currently the issue is in the testing phase by ServiceNow internal dev team.

 

The Fixed Target is as follows:

  • Utah - Fixed
  • Tokyo - Ready for Testing in the release branch (Tokyo Patch 3)

 

There is no workaround shared by the dev team, apart from disabling the script include TaskSLAFlowSNC, as discovered by me originally.

View solution in original post

2 REPLIES 2

Henri Muldre
Tera Guru

Update:

I found the following from syslog table (*censored User ID* is my user ID of the instance):

Cancelling transaction BackgroundProgressJob - *censored User ID* (SLA stage is completed): Thread glide.scheduler.worker.4 (*censored User ID*, glide.scheduler.worker.4), after 263484ms

 

Upon looking closer, I found that the OOB script include "TaskSLAFlowSNC" is causing this "SLA stage is completed". I compared the script between Tokyo and Rome - script was identical.

When I disabled (active=false) the script include and ran the ATF suite/test again, it did not fail this time.

 

Same issue does not happen in Rome with the same script include.

I created a NowSupport case and I'm currently waiting to hear back from them.

Henri Muldre
Tera Guru

Update!

 

To anyone scratching their heads at this:

I heard back from ServiceNow NowSupport and they said that they were able to reproduce this issue in their OOB Tokyo instance. They created a problem ticket and currently the issue is in the testing phase by ServiceNow internal dev team.

 

The Fixed Target is as follows:

  • Utah - Fixed
  • Tokyo - Ready for Testing in the release branch (Tokyo Patch 3)

 

There is no workaround shared by the dev team, apart from disabling the script include TaskSLAFlowSNC, as discovered by me originally.