I’m having trouble with my Azure Application Gateway. I increased the backend request timeout from 30 to 900 seconds to avoid timeouts for long-running tasks in my AKS cluster. But every time I check later, it’s back to 30 seconds!
Has anyone else run into this? I’m stumped on how to make this change permanent. Is there some automatic reset happening? Or am I missing a step to save the configuration?
I’d really appreciate any tips on keeping custom timeout settings. It’s frustrating to keep manually changing it back. Thanks for any help!
hey, i’ve dealt with this before. check ur ARM templates or terraform configs if ur using them. they might be overwriting ur changes. also, double-check any CI/CD pipelines. sometimes they reset stuff without u knowing. hope this helps!
oh wow, that sounds frustrating! have u tried checking for any scheduled maintenance or auto-scaling policies? they could be resetting your settings. also, maybe theres a bug in the azure portal? might be worth trying to set the timeout through azure CLI or powershell instead. let us know if u figure it out!
I’ve encountered a similar issue with Azure Application Gateway timeout settings reverting, and it appears that automated deployment tools or configuration management might be the cause. In my experience, ensuring that your Infrastructure as Code scripts or ARM templates correctly specify the timeout value is essential. I found that reviewing Azure Policies to ensure they are not enforcing defaults and using Azure PowerShell or CLI for adjustments instead of the portal made a difference. Additionally, setting up Azure Monitor alerts helped identify when changes occurred, which improved my troubleshooting process.