In the integration_settings Entity, there is a settings_key=stopProcessing. This setting is checked each time the timer runs on any node. If the setting_value > 0 for this setting_key=stopProcessing, then the integration will not run any flows. This is the equivalent of “turning off” or stopping the integration. If the setting_value = 0, then the integration will process reactions in the queue.
The scenarios where turning off or on the integration may include but are not limited to:
There are a 3 approaches for stopping the integration:
update integration_settings set settings_value=1 where settings_key="stopProcessing";
3. To turn on the integration, run the following SQL:
update integration_settings set settings_value=1 where settings_key="startProcessing";
4. Remember to turn the integration back ON after it has been turned off.
To start the integration, follow the same steps as above except use the instructions for starting the integration. When starting and stopping the integration, the listeners do NOT need to be restarted as they do for any other integration setting changes.
If you are turning the integration off to restart the server, be sure to monitor the cfg_obj table to ensure that the node_ip column is cleared out for all records before restarting.
The polling timer checks the stopProcessing flag when it first begins running. If the stopProcessing flag is toggled on while the timer is running, the timer will finish out its tasks before the integration stops, so you may need to monitor the cfg_obj table and wait for all the flows to finish running before restarting. When all values in the node_ip column are null, the server is ready to restart.