pfSense

Applying some actions takes time (from tens of seconds to several minutes). In the meantime, the web interface hangs (browser says "waiting for…") or crashes (nginx says "502 bad gateway").

• With dozens of VLANs on a unique lagg, modifying the physical network interfaces constituting the lagg takes several minutes (it's normal: in background, pfSense re-creates all interfaces (lagg0.X, lagg0.Y, etc.). During, the web interface is unavailable ("waiting for…") ;
• "502 bad gateway" during CARP failover (by clicking on "temporarily Disable CARP" in Status > CARP or by shutting down the master or by removing the network cable) ;
• "502 bad gateway" during some other day-to-day greedy actions but my brain memory is failing…

Can we imagine to execute greedy actions in background in a dedicated thread / external script (with tools like rabbitmq?) and display informative message? So the web interface will always be available.
Reload firewall rules and aliases is a good example: actions are done asychronously and the web interface stay available.