"Invalid Task ID" while opening a Visual Task Board

Shyam Gupta
Kilo Explorer

‎07-25-2022 10:10 AM

"Invalid Task ID" while opening a Visual Task Board for Scheduled Changes. I cannot open the board, and I ultimately have to recreate the board from scratch. I was able to access this board for the last 6 months.

find_real_file.png

Labels:
Preview file
6 KB
0 Helpfuls
  • 2,298 Views
11 REPLIES 11

kimfranz
Giga Expert

‎07-26-2022 11:00 AM

Hi, I am getting this too for one of my users on the Incident table. If you have the filter that the VTB is using saved as a favorite, you can quickly see which records might have caused the issue. Odd thing is that if you do Show Visual Task Board off of that filter to create a new VTB, it shows fine. So far it seems to be Incidents which are integrated in or Incidents which are systematically created from monitoring Event. (so no human created Incidents seem to be the cause.)

So I am following this thread to see if there is any hints for you which could help me. 🙂

BTW: We are on Rome version

0 Helpfuls

Shyam Gupta
Kilo Explorer
In response to kimfranz

‎07-26-2022 12:17 PM

Hi Kim. Once I get the error, the page redirects back to the dashboard which has all VTB's.

It doesnt even allow me to go to the VTB to make any changes. Only option I have is to create a new VTB.

 

0 Helpfuls

kimfranz
Giga Expert
In response to Shyam Gupta

‎07-27-2022 01:11 PM

Hi Shyam,

Understood, that is our experience too. 

  • Do you also have the filter which is used for the 6 month old VTB saved as a favorite separately? 
    • This would be handy to go quickly to see which change record is not showing in the VTB. 
  • When you create the new VTB, does it continue to work well for you but then also stops working after some time? (getting the error "Invalid Task ID" again?)
    • We are finding that new records which qualify for the VTB are the records which seem to be causing the issue, but when they progress along their lifecycle and conditions change on them, the existing VTB starts working again. 

I still have not found root cause, an older query on the community said it was caused by a business rule, but I do not think that is the case for us. 

I will share as I learn more.

0 Helpfuls

kimfranz
Giga Expert

‎07-28-2022 12:33 PM

Hi Shyam,

I found out more about the error, but not yet the root cause or fix yet. 

For my case, I went to look at the syslog errors for the user (created by), Level = Error, Created = day issue occurred. 

I found that the message indicated: Unique Key violation detected by database

" Duplicate entry '<sys_id-of-vtb_board>-<sys_id-of-incident>' for key 'board' "

When I learn more, I will let you know. 

This might be different for you, but have someone look at the syslog table for you if you cannot yourself. 

0 Helpfuls