Common Error Messages and Causes<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Logik is constantly working to improve our error messaging to give more information to a user in order to diagnose and correct any issues. However, there are some error messages that are not very user-friendly. This article is a list of some of these error messages and potential causes to help know where to look if a user receives one of these errors. Unable to roll back to previous state. Often this error is related to a table lookup. Check to ensure that any tables in a lookup exist in your Logik environment. Check the syntax of your lookup to ensure that the table column headers exactly match your query script. Capitalization, spelling, etc. could be off causing a table lookup to fail and throw this error. This could also involve circular logic being triggered by a given field change. One example that might cause this is a Field being in both the condition and action of a rule. If this error is seen directly after selecting a Field Option, then check the rules related to that Field (specifically by last modified date) to help isolate the cause. Error: Your rules are running beyond the stipulated time. Please contact your system administrator. This also typically means some rules are running in an infinite loop. Rule may have the same field as part of conditions and actions(ex. Determination rule to set a field value conditioned on a value already in that field.) Helpful to diagnose by getting the click path to fire error then inactivating specific(usually recently modified) rules one at a time to see if the error continues to be encountered. “...Index '0' is out of bounds…”: This almost always means they’re trying to reference a list or an array that is empty. In a literal sense, the error message is trying to reference the first index (0) of the list or array, and is finding that 0 is beyond the bounds of the list or array (in other words, it is empty). Some likely culprits: There is something misspelled in a table query. The query references a cfg value that hasn’t been set yet due to the rule conditions. The lookup query returned zero results (everything might be spelled right…. Just might not have any results in the table that match). Null checks on arrays are your friend! Cannot read properties of undefined (reading 'map'). Occurs on buyside when user opens Logik config Review the layout file. Make sure that the reference(s) to set variable name(s) is/are accurate.