Skip to content

v3.1.3

Release Notes – Version 3.1.3

Improvements

  • The API now starts immediately, even if the database or RabbitMQ is not reachable yet. The connections are checked every 10 s in the background; database migrations and the remaining initialization run as soon as both are available.
  • While the API is still initializing, requests to the API return 503 Service Unavailable. The web frontend is still delivered, and the login page shows a message that GroundControl is still starting.
  • The repeated connection warning during startup is logged without the stack trace (the full exception is logged on log level Verbose).

Bug Fixes

  • Fixed the API Windows Service failing to start (error 1053) when the database or RabbitMQ was not reachable at startup. The service did not report the running state to Windows in time and was terminated, so no retries happened.
  • Fixed the login page showing [object ProgressEvent] when the API could not be reached.
  • Fixed a RabbitMQ connection being left open by the startup connection check.

Breaking Changes / Notices

  • If the initialization fails after the connections were established, the API logs an error and stops. Configure the recovery options of the Windows Service (e.g. "Restart the service") so it is restarted automatically.