On a regular interval steamcmd will have to be updated. This is done (and only done..) when steamcmd is executed. This event however should be logged that in the case of a (too) long running request, it can possibly be traced back in the log that steamcmd updates were the cause of it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
On a regular interval
steamcmd
will have to be updated. This is done (and only done..) whensteamcmd
is executed. This event however should be logged that in the case of a (too) long running request, it can possibly be traced back in the log thatsteamcmd
updates were the cause of it.In the following issue the suggestion is made to use HTTP status code 202: https://stackoverflow.com/questions/9794696/how-do-i-choose-a-http-status-code-in-rest-api-for-not-ready-yet-try-again-lat. The official description of the status code seems very reasonable and it's a 2xx code which means load balancers or clients don't necessarily have to see it as a failed request.
With this we can gracefully process updates to
steamcmd
without the API failing.