{}

Our Brand

{"support":{"yesButton":"yes","noButton":"no","feedback":{"title":"What can we do to improve?"},"submitButton":"Submit","successMessage":"Thank you for your feedback","title":"Did this answer your question?","feedbackPercentLabel":"of people found this helpful","captcha":{"error":"Please tick the box"}}}

Search FAQs

{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}

When multiple critical events occur, why does PowerChute Network Shutdown 3.0.1 not shut down using the shortest delay value in one of the events?

Issue:
When multiple critical events occur,  PowerChute Network Shutdown does not shut down using the shortest delay value assigned to one of the events.
For example, you configure PowerChute Network Shutdown v3.0.1 with a shutdown delay of 300 seconds for event 1 and 120 seconds for event 2.  If event 1 occurs first and then event 2 occurs, PowerChute will wait 300 seconds before starting the shut down sequence instead of using the shorter delay of 120 seconds.

Product Line:
PowerChute Network Shutdown version 3.0.1

Environment:
Impacts all Windows, Linux and Unix operating systems supported for PowerChute Network Shutdown v3.0.1.

Cause:
A change made to PowerChute Network Shutdown v3.0.1 introduced this issue. PowerChute Network Shutdown versions 3.0 and earlier are not impacted by this and do not require this update.

Solution:
Upgrade to PowerChute Network Shutdown version 4.x
Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.

Can't find what you are looking for?

Reach out to our Customer Care team to receive information on technical support, assistance for complaints and more.