IGN0004 - Ignite no longer running after a long period of time

Expand / Collapse

IGN0004 - Ignite no longer running after a long period of time

Article ID: 51999 - Last Review: July 19, 2013


If left running overnight, Ignite becomes unresponsive or responds very slowly. It cannot receive ACD content or acknowledge and change agent or employee states.




Agents cannot take ACD calls while Ignite is in this state.


If Ignite is left running overnight, a server maintenance cycle could have taken place, leaving Ignite in a non-functional state. To resolve this issue, shut down and restart Ignite and sign in again.

We recommend you exit Ignite at the end of each agent's shift to avoid this issue. Following server maintenance, the next time Ignite is launched, any changes to the Enterprise Server configuration will be updated automatically.

To exit Ignite
1. Click the Power button to display Side bar actions.
2. Click the Exit command to sign out and shut down Ignite. Your agent will automatically be signed out of ACD availability.

You must exit Ignite to ensure Make Busy or Do Not Disturb statistics do not get created erroneously at the end of the agent's shift.


7.0 I5 (Beta II) 

Keywords: IGN0004 ignite running long period overnight maintenance functional restart hang hung

Rate this Article:

Add Your Comments

Name: *
Email Address:
Web Address:
Verification Code:

Last Modified:Tuesday, September 03, 2013
Last Modified By: andrew_montpetit
Article not rated yet.
Article has been viewed 9,005 times.