Troubleshooting Model Failure Messages

Please find a list of model errors that might appear in the Job Error Log and their associated resolutions.

Error – Preprocessor run failed: not enough values to unpack (expected 2, got 1)

Resolution – Please check to see if a scenario item was built where an action does not reference a column name. Scenario Actions should be of the form ColumnName = …..

Error – Preprocessor run failed: unterminated string literal (detected at line 1)

Resolution – Please check to see if there is a string in the scenario condition that is missing an apostrophe to start or close the string

Error – sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at “DB_NAME” (13.86.125.217), port 6432 failed: SSL SYSCALL error: EOF detected

Resolution – This indicates an intermittent drop in connection when reading / writing to the database. Re-running the scenario should resolve this error. If the error persists, please reach out to support@optilogic.com.

Have More Questions?

Table of Contents

Troubleshooting Model Failure Messages

Error – Preprocessor run failed: not enough values to unpack (expected 2, got 1)

Error – Preprocessor run failed: unterminated string literal (detected at line 1)

Error – sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at “DB_NAME” (13.86.125.217), port 6432 failed: SSL SYSCALL error: EOF detected

Troubleshooting Model Failure Messages

Error – Preprocessor run failed: not enough values to unpack (expected 2, got 1)

Error – Preprocessor run failed: unterminated string literal (detected at line 1)

Error – sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection to server at “DB_NAME” (13.86.125.217), port 6432 failed: SSL SYSCALL error: EOF detected

Have More Questions?

Contact Support

Contact Sales

Visit Frogger Pond Community