Support Center > Search Results > SecureKnowledge Details
Cannot change Aggressive Aging timeout on created/cloned service
Symptoms
  • When trying to change the Aggressive Aging timeout value of a service (cloned or new) to a value lower than the Stateful Inspection default session timeout, a message pop-up says: "The value must be in range..."
Solution
Note: To view this solution you need to Sign In .