# Ignition Bouncing between 40%-70% and sometimes unresponsive **URL:** \ **Category:** Ignition\ **Created:** [June 9, 2017, 6:53pm UTC](https://forum.inductiveautomation.com/t/ignition-bouncing-between-40-70-and-sometimes-unresponsive/14488 "2017-06-09T18:53:16Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![brandon222](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@brandon222](https://forum.inductiveautomation.com/u/brandon222)\ **Post date:** [June 9, 2017, 6:53pm UTC](https://forum.inductiveautomation.com/t/ignition-bouncing-between-40-70-and-sometimes-unresponsive/14488/1 "2017-06-09T18:53:17Z")
We currently have it setup connected to a PLC and running about 30 000 tags. I noticed that the CPU on the ignition gateway is running between 40% - 67%. Also sometimes when a button is pressed it does not go through and must be pressed multiple times until it finally goes through. The error on the logs says “write time out”. Does anyone have any ideas what it could be? Here is the logs: Logger Time Message ProjectRunner 09Jun2017 14:55:13 Tried to perform RPC operation on an unrecognized session. May indicate that the previous session was lost. Creating RPC listener for new session id. ProjectRunner 09Jun2017 14:46:31 Tried to perform RPC operation on an unrecognized session. May indicate that the previous session was lost. Creating RPC listener for new session id. Route 09Jun2017 14:24:45 Error handling route. …com.inductiveautomation.ignition.gateway 09Jun2017 14:17:20 Starting up client project monitor. project=Paramalat\_Winnipeg, uuid=8f605af6-7bde-6f75-428b-506455d8f7dd, editCount=3790, scope=4, version=Published SAP\_HTST\_Que1\_GI1 09Jun2017 14:07:26 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 13:07:23 CDT 2017]]. SAP\_HTST\_Que2\_GI1 09Jun2017 14:07:26 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 13:07:23 CDT 2017]]. SAP\_HTST\_Que3\_GI1 09Jun2017 14:07:26 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 13:07:23 CDT 2017]]. Provider 09Jun2017 14:06:28 [[default]Parmalat/HTST1/Production\_Control/HTST1/Water\_To\_Prod\_PB] Error writing to OPC address [[Ignition OPC-UA Server]ns=1;s=[Parmalat\_Main]HTST1Prod.WP\_Button]. Result code: [Bad\_Timeout] The operation timed out. WriteContext 09Jun2017 14:06:28 Write timed out. SynchronousWrite 09Jun2017 14:06:28 WriteItem did not receive value before timeout: HTST1Prod.WP\_Button Provider 09Jun2017 12:07:11 [[default]Parmalat/Engineering\_Values/Past\_AA\_CIP\_EV/EV 21] Error writing to OPC address [[Ignition OPC-UA Server]ns=1;s=[Parmalat\_Main]PastAEV[21]]. Result code: [Bad\_Timeout] The operation timed out. WriteContext 09Jun2017 12:07:11 Write timed out. SynchronousWrite 09Jun2017 12:07:11 WriteItem did not receive value before timeout: PastAEV[21] Report\_ReportHTST1 09Jun2017 11:59:11 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:59:08 CDT 2017]]. Report\_ReportFracCartonFiller 09Jun2017 11:59:11 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:59:08 CDT 2017]]. Production\_HTST2\_Que1\_HTSTParameters\_PLC 09Jun2017 11:57:01 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Production\_HTST2\_Que3\_HTSTParameters\_PLC 09Jun2017 11:57:01 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Production\_HTST2\_Que2\_HTSTParameters\_PLC 09Jun2017 11:57:01 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportRecoveryDarkSupplyLineBlend 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportCrtnAFiller 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportRecoverPastTankLine 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportJugFiller 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportT806 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportT103 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportT204 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportRecoveryDarkToBlendingLine 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportRecoveryLFHFSupplyLineBlend 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportSkimBlendLine 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportHTST2 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportT204Line 09Jun2017 11:57:00 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. Report\_ReportHTST2Line 09Jun2017 11:56:59 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. Report\_ReportBlendHTSTLines 09Jun2017 11:56:59 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. Report\_ReportT805 09Jun2017 11:56:59 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. SAP\_HTST\_Que1\_GI1 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_HTST\_Que3\_GI1 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_HTST\_Que2\_GI1 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Milk\_Receipt 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI14 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI13 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI10 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI8 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI12 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI9 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI1 09Jun2017 11:56:58 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:54 CDT 2017]]. SAP\_Milk\_Receipt 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_OrderConfirmationHeaderFull 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI15 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI5 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI6 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI2 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GI3 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_Mixing\_GR1 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[0, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_HTST\_Que1\_GI1 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_HTST\_Que3\_GI1 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. SAP\_HTST\_Que2\_GI1 09Jun2017 11:56:57 Trigger did not evaluate - source item currently has bad quality [[false, Unknown, Fri Jun 09 10:56:53 CDT 2017]]. …com.inductiveautomation.ignition.gateway 09Jun2017 11:18:33 Starting up client project monitor. project=Paramalat\_Winnipeg, uuid=8f605af6-7bde-6f75-428b-506455d8f7dd, editCount=3790, scope=4, version=Published …com.inductiveautomation.ignition.gateway 09Jun2017 11:17:28 Starting up client project monitor. project=Paramalat\_Winnipeg, uuid=8f605af6-7bde-6f75-428b-506455d8f7dd, editCount=3790, scope=4, version=Published ---
**Author:** ![martinel3746](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@martinel3746](https://forum.inductiveautomation.com/u/martinel3746)\ **Post date:** [August 25, 2017, 2:54pm UTC](https://forum.inductiveautomation.com/t/ignition-bouncing-between-40-70-and-sometimes-unresponsive/14488/2 "2017-08-25T14:54:06Z")
I started seeing “Tried to perform RPC operation on an unrecognized session” warnings too but I haven’t seen any performance issues …yet… I did notice that CPU usage spikes are much higher when I am viewing the Logs with a filter, and it spikes really high when the filter starts ‘jumping’ out of control (for example if you filter with two or more space delimited entries). I don’t see a correlation yet. I’ll be watching this topic with interest. ---
**Author:** ![james\_electriceng](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@james\_electriceng](https://forum.inductiveautomation.com/u/james_electriceng)\ **Post date:** [October 3, 2022, 6:48am UTC](https://forum.inductiveautomation.com/t/ignition-bouncing-between-40-70-and-sometimes-unresponsive/14488/3 "2022-10-03T06:48:23Z")
I have the same issue but no memory, cpu or thread spike. How did you fix this? nothing looks wrong but designer takes an incredibly long time to open views. ---
**Author:** ![james\_electriceng](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@james\_electriceng](https://forum.inductiveautomation.com/u/james_electriceng)\ **Post date:** [October 3, 2022, 8:04am UTC](https://forum.inductiveautomation.com/t/ignition-bouncing-between-40-70-and-sometimes-unresponsive/14488/4 "2022-10-03T08:04:09Z")
Signing everyone out of the host machine and restarting the host machine fixed this problem for me. Not sure what caused it but happy that it is back to normal. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 3, 2022, 12:25pm UTC](https://forum.inductiveautomation.com/t/ignition-bouncing-between-40-70-and-sometimes-unresponsive/14488/5 "2022-10-03T12:25:21Z")
Don't ever run a designer on your host machine if it is easily overloaded (or ever at all, IMNSHO). If you need to do maintenance via RDP, log in, get it done, and log right back out. Don't leave a user session running. ---
**Author:** ![brandon222](https://avatars.discourse-cdn.com/v4/letter/b/ee59a6/32.png) [@brandon222](https://forum.inductiveautomation.com/u/brandon222)\ **Post date:** [October 16, 2022, 4:28am UTC](https://forum.inductiveautomation.com/t/ignition-bouncing-between-40-70-and-sometimes-unresponsive/14488/6 "2022-10-16T04:28:06Z")
Hey turns out my issue was PLC and DB issues. Some how a null was sent in from the DB to the PLC through ignition at some point which caused everything to crash and the only way to fix this is to reboot the server. Sadly I never found a solution more then never allowing a null. If for some reason I need to send anything related to a null. I would just send a 0. Issue hasnt happened since. Hope that helps.