Onsite yesterday setting up a client's Windows 2016 Server with FileMaker Server 17, I had the admin console timeout on me despite being partway through configuring a backup schedule.
Upon logging back in, it had lost the most recent settings I was entering into the scheduled when it logged out. I was working continuously, without any break, systematically working through the server configuration when it happened. The last mouse click had been to create this new schedule and I was subsequently entering the folder path and frequency.
Most systems I'd expect timeout after an idle period, but wondered whether anyone else has seen this and whether this is standard behaviour?