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

[DZerkle]

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.

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?

[ABurt]

Hello,

I assume this a field-change-triggered script? What do you have selected for the ""Run triggered script after incident is modified"?

You will not need to specify the "CustomFields" in the setIncident command either. You can use the system name for the field. In your case it would (most likely) be:

demisto.executeCommand("setIncident", {"id":child_case_id, "falsepositive":True})

Regards

Adam

[DZerkle]

I don't even have that checkbox.  Where is it?  We're running 6.0.

[DZerkle · Accepted solution]

It looks like the checkbox is only there for version 6.1.

The workaround is to leave out the 'id':child_case_id  in the setIncident command and leave out the "incidentId":child_case_id  in the linkIncidents command.  This will default to using the current incident.

It may be that you have to use the ID, as is the case with the linkIncidents command.  In this case, triggered scripts need to use demisto.investigation()['id'] to get the incident ID.  They can't use demisto.incidents()[0]['id'].

[DZerkle]

The solution above turns out to be only partial.  Leaving out the incidentId field for the linkIncidents command causes the command to do nothing.  Putting it back in re-generates the DB version errors.  Running the trigger script from the command line works perfectly.

So, I don't have a way to modify linked cases in a triggered script in 6.0.  Anyone know?

[ABurt]

If you leave out the "id" field in the setIncident command, it will execute within the current incident (it assumes the current incident is the id).

Is the script executing from within an existing incident, or is the script attemping to update a different incident?

[DZerkle]

We just upgraded to 6.1, so I revisited this matter.  It's not much better.

The DB Version errors no longer appear.

If I leave "Run triggered script after case is modified" unchecked, the triggered script correctly updates other fields with the setIncident command.

If I check that box, the other fields do not update, even though the war room says that they're updated.

Whether I check that box or not, and no matter how it is called, the linkIncidents command does nothing when run from a triggered script.  It works as expected if run from a script launched by a button or the command line. 

Can you confirm the above?  The docs mention nothing about linking incidents from triggered scripts.

[ABurt]

The automatoin script that you have created to link the incidents, can you confirm who it is running as? By default it's "limited user".

This may be affecting the outcome.

[DZerkle]

It was set to "limited user".  I tried setting it to "DBot".  No change in behavior resulted.

I have the exact same script triggered by a button and triggered by a field change.  It works fine when triggered by the button.

[ABurt]

Can you post the contents of the script?