Upgrading from Madrid to Orlando causes issues with running flowsDescriptionWhen upgrading from Madrid to Orlando, and skipping New York, flows get stuck in the 'Queue' state. This occurs because the Java code is expecting a table to exist that will only exist when the upgrade finishes. The issue was observed in Orlando because of a flow plan versioning change that caused all flows that run to have flows recompiled.Steps to Reproduce Madrid DB Orlando code upgrade test. 1. Get a TD instance off M2. Create a flow with custom action that has some inputs, create some more flows with combination of actions like create record, log, send email etc. Keep incident created as a trigger2. Do an upgrade with code option and uncheck auto upgrade to keep db of madrid3. Create an incident and see if the flow is getting triggered. Make sure to test by creating incident and not just by Test button.com.glide.db.GlideSQLException: FAILED TRYING TO EXECUTE ON CONNECTION glide.15 (connpid=12934): SELECT null FROM action_input_action_instance action_input_action_instance0 /* sabredev2014, gs:glide.scheduler.worker.0, tx:c7673621db221010b5e41c791396194d */Syntax Error or Access Rule Violation detected by database ((conn=12934) Table 'sabredev2_2.action_input_action_instance' doesn't exist)at com.glide.db.DBIError.wrapAndThrow(DBIError.java:153)at com.glide.db.DBIError.handleException(DBIError.java:86)at com.glide.db.DBI.executeStatement(DBI.java:1110)at com.glide.db.DBQueryExecutor.executeStatement(DBQueryExecutor.java:220)at com.glide.db.DBQueryExecutor.executeStatement(DBQueryExecutor.java:210)at com.glide.db.DBQueryExecutor.execute(DBQueryExecutor.java:57)at com.glide.db.DBQuery.executeAsResultSet0(DBQuery.java:355)at com.glide.db.DBQuery.executeAndReturnTable(DBQuery.java:332)at com.glide.db.DBAction.executeNormal(DBAction.java:256)at com.glide.db.DBAction.executeAndReturnException(DBAction.java:210)at com.glide.db.RDBMSQueryContext.executeQuery(RDBMSQueryContext.java:42)at com.glide.db.DBQuery.execute(DBQuery.java:2705)at com.glide.db.meta.Table.queryBasic(Table.java:338)at com.glide.db.meta.Table.query(Table.java:206)at com.glide.script.GlideRecordITable.query(GlideRecordITable.java:108)at com.glide.script.GlideRecord.query0(GlideRecord.java:3327)at com.glide.script.GlideRecord.get(GlideRecord.java:1524)at com.glide.flow_design.action.data.ActionInputActionInstanceGlideRepository.getActionInputActionInstanceByInputId(ActionInputActionInstanceGlideRepository.java:71)at com.glide.flow_design.action.providers.ActionInputActionInstanceGlideProvider.getActionInputActionInstanceByInputId(ActionInputActionInstanceGlideProvider.java:49)at com.glide.flow_design.helpers.FDParameterHelper.setDynamicOptionValues(FDParameterHelper.java:84)at com.glide.flow_design.helpers.FDParameterHelper.parameterMapFromEDMap(FDParameterHelper.java:44)at com.glide.flow_design.helpers.ComponentInstanceHelper.elementsToVars(ComponentInstanceHelper.java:239)at com.glide.flow_design.helpers.ComponentInstanceHelper.getInstanceValues(ComponentInstanceHelper.java:178)at com.glide.flow.data.ActionInstanceGlideRepository.getActionInstanceValues(ActionInstanceGlideRepository.java:124)at com.glide.flow.data.ActionInstanceGlideRepository.getActionInstance(ActionInstanceGlideRepository.java:72)at com.glide.flow.data.ActionInstanceGlideRepository.getActionInstancesByFlowSysId(ActionInstanceGlideRepository.java:93)at com.glide.flow.data.FlowGlideRepository.getFlowBySysId(FlowGlideRepository.java:183)at com.glide.flow.providers.FlowGlideProvider.createFlowInstance(FlowGlideProvider.java:325)at com.glide.flow.providers.FlowGlideProvider.getFlow(FlowGlideProvider.java:237)at com.glide.flow_trigger.engine.FlowPlanRetriever.retrieve(FlowPlanRetriever.java:116)at com.snc.process_flow.engine.ProcessHubEventHandler.doStartFlow(ProcessHubEventHandler.java:170)at com.snc.process_flow.engine.ProcessHubEventHandler.process(ProcessHubEventHandler.java:73)WorkaroundAttached are the sys_dictionary entries that get put into the instance once upgrade is complete. Putting them in before upgrade should prevent the problem from occurring. The fix for this issue has been backported to Paris Patch 2, Orlando Patch 5 Hot Fix 2, and Orlando Patch 8. Related Problem: PRB1419714