Error: DB Version '##' and Insert version '##' do not match for id: ##### on bucket [] [incidents] (15)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Error: DB Version '##' and Insert version '##' do not match for id: ##### on bucket [] [incidents] (15)

L2 Linker

I have a trigger script automation that updates the linked incidents of an incident.  The update works, but then it produces the following error and refuses to update the field that triggered the automation.

 

DZerkle_0-1614912375236.png

 

 

The script works fine if I run it from the command line.  It's only when a triggered script runs that there's a problem.

 

Here's a sample that causes a problem.  If I comment this line out, the field updates just fine.

 

demisto.executeCommand("setIncident", {'id':child_case_id, "customFields":"{\"False Positive\":\"True\"}"})

 

 

Anyone know what's going on and to fix this?

19 REPLIES 19

Yes, I created a new button for the "Create new parent" thing.  I tried to do it via the triggered script.  I could get it to link to create the new incident and to link to it (using demisto.investigation()['id']).  However, that would require updating the field that just got changed from "Create new..." to the name of the new parent, and I couldn't get that to work.  That's when I gave up and made the button.

 

You suggest a delay.  I'm not sure where you want me to put it.  Here's the current sequence.  Where should I put it?

 

  1. User clicks button
  2. The button graphic changes to a swirly circle
  3. Button script creates new parent incident
  4. Button script calls setIncident to successfully update falsepositiveparent field with the name of the new incident
  5. The trigger script for the falsepositiveparent field activates
  6. The trigger script computes its own ID using demisto.investigation()["id"].
  7. The trigger script (using that ID) successfully unlinks any old incidents and links to the new parent.
  8. The trigger script attempts to update the falsepositive boolean field using setIncident, but hangs, instead, and never finishes.
  9. The button graphic stays a swirly circle forever.
  10. I attempt to close the case manually, filling in required fields for the pop-up form.  I get no errors.
  11. The case stays open forever.

If steps 1-4 are replaced by a user clicking on the falsepositiveparent field to update it, everything works perfectly.  So, this smells like a deadly embrace bug where the button and the trigger script are waiting for each other.

 

Note that there are no loops.

 

The workaround is just to stop trying to update the falsepositive field and make the user do it manually.  That's not a huge problem, so don't break your back trying to figure this out in a rush.  It's worth figuring out eventually, though, as the documentation for the restrictions on trigger scripts should be more complete, and also this might be an actual bug.

Also, I'm very impressed that your triggered script in the video managed to close the incident.  On reading the documentation for trigger scripts, I see that "Trigger scripts cannot close incidents.".

Sorry, I did not meana delay in the script iteself. I meant the timeout of the script:

ABurt_0-1616587479981.png

 

If there is something "locking up" the incident in the script, then it will unlock after (for example) 5 seconds.

Ha, I did not notice that in the documentation. I have informed our technical writers about it and they will check with engineering before updating the docs. Well spotted!

The timeouts for all the scripts are set to the default, 180 seconds.  The lockup seems to be forever.

 

I've asked our admin to file a support ticket to get help closing the broken incidents.

  • 10889 Views
  • 19 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!