When I try to pause an agent and enter a timeout of more than 1440 minutes (1 day), I am taken to a generic 404 page with no information about the error.
IMO it should be possible to pause an agent for as long as I want, but if timeouts longer than a day aren’t supported then there should at least be a specific error message not a 404.
Are you still able to get logs for the agent error and email it to us at support@buildkite.com? Additional details to your pipeline or any previous build url running on the agent before it was paused would also be helpful for us in investigating this issue further.
Hi @190n - I just took another look at this and found that I can reproduce this issue. After further investigation, I found that 1440 minutes is the upper limit on how long an agent can be paused for. I’ve submitted a bug for us to provide a more useful error in the UI in this case. Thanks for bringing it to our attention!
Thanks, a better error will certainly be appreciated. But is there a reason for that upper limit? I really wanted to pause the agent indefinitely as it could only be unpaused once I resolved and fixed an issue, which doesn’t have anything to do with the time.
Following up to let you know we’ve fixed the bug with the 404 page appearing when trying to set a pause timeout of greater than 1440 minutes. It will now add an error message to the top of page:
The reason for the upper limit of 1440 minutes is a conscious effort to avoid Agents being paused indefinitely, but continue to run and potentially be costing money whilst not picking up any jobs.
But will mention it is possible to pause dispatch of the Cluster Queue indefinitely, though aware this would affect multiple Agents receiving new Jobs to run. Alternatively, disconnect the problematic Agent as it can always be reconnected after any issues are resolved on it.