Symptoms
The timeout cannot be changed.
Cause
This is a known issue for SaaS environments: they are locked for 30 minutes because an environment variable is set and overwrites the registry value.
Workaround
N/A
Affected version
All SaaS versions
Resolution
A new feature that will allow control timeout for all environments from the cloud portal will be released in the future.
No ETA has been provided yet.
Comments
0 comments
Please sign in to leave a comment.