Hi, am running the desktop version 6.3.22 with local autorouter version 0.8.1.0. When invoking the autoroute function in easyeda, it hangs at 0% with the local autorouter reporting : \-\-\-\-\-\-\-\-\-\-\-\-\-Connection established\-\-\-\-\-\-\-\-\-\-\- Start routing... Routing \-\-\-\-\-\-\-\-\-\-\-\-\-Connection closed\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- The weird thing is that if I cancel and restart autorouting in EASYEDA, same thing happens. However, if I invoke a autorouting again in EASYEDA (duplicate), it completes the autorouting in seconds with an error complaining I cannot start another autorouting job before the first one completes. I have been using this workaround to get the job done, however, this is pointing to some connection management issue between EASYEDA desktop software and the local autorouter. Upon digging deeper, my question is - what do the following config parameters in the local autorouter mean. These are settings under the config/local subdirectory in the main.json file. { "web": { "ip": "127.0.0.1", "port": 3579, "idle": 60000 }, "router": { "min_timeout": 300000, "min\_progress\_interval": 2000\, "keep_heartbeat": 5000, "max\_route\_retry": 10 } } ip & port are self explanatory\. What do idle\, min\_timeout\, min\_progress\_interval\, keep\_heartbeat and max\_route\_retry control ? Kind regards, -M