Is it expected that
rest/db/status for a folder returns a 404 with the body “folder is not running” on startup?
The behaviour used to be that the API wouldn’t start at all until all of the folders had started. However I’m now getting reports of a 404 when trying to fetch
rest/db/status after startup.
If this is an intentional change, is there a good way of telling when Syncthing has started, before polling
rest/db/status for each folder? Or should I sit there polling all folders until they all return non-404? Does a 404 from this endpoint always mean “temporarily unavailable”, or are there cases where a 404 here is a genuine, unrecoverable error?