Update Commit Log message, what does it mean Changes for table var__m_atf_input_variable for an update Set

[Andrew Payze]

Hi,

I have built update sets on London.   I am testing them on Madrid and get the following error for all update sets. it appears that the features in the update sets are deployed and working as expected, however wanted to know if this error is something we have to worry about

Update Commit Log message, 

Changes for table var__m_atf_input_variable_a5836cd7739023005a59e5c754f6a700 failed to commit

Thanks

Andrew

[Alikutty A]

Hi,

I have come across similar error messages even after successful commit and it is mainly noticed if your update set is large and takes long time to commit. You need to make sure all changes to related to specified update is committed properly and everything is testing working.

Thanks!

[tstocking]

We are starting to experience the same errors since upgrading from Madrid Patch 1 to Patch 4. Did you end up opening a case?

[Tyler Herman · Accepted solution]

Check out the official answer from ServiceNow in https://hi.service-now.com/kb_view.do?sysparm_article=KB0752190.

For what it's worth, I was getting this error except on a different table "var__m_var_dictionary_b99518770a0a0b3472c1802342a11fbf". I had a currency field as an input variable on a workflow. I changed it to a decimal field instead and the issue ceased.