Call to dptools function sleep in outbound routes

[Adrian Fretwell]

Does anyone know why we now have a call to the sleep function for ${sleep} seconds, when we add a new outbound route? See the screenshot below:




The reason I ask is because I recently added a new domain to an older (version updated to master in January) box and noticed these errors in the log file:

25607776-a79a-4d4d-a66f-e97c613bb092 2020-09-07 13:19:43.905129 [ERR] mod_dptools.c:2399 No timeout specified.
25241ecf-4eb6-431d-9781-dcd6012f9a9c 2020-09-07 13:20:08.245129 [ERR] mod_dptools.c:2399 No timeout specified.
eb523423-6583-486a-a807-43e8e79dc344 2020-09-07 13:22:55.985099 [ERR] mod_dptools.c:2399 No timeout specified.
c4d289e9-56e5-45bb-8358-95ab4fa89a19 2020-09-07 13:23:36.705094 [ERR] mod_dptools.c:2399 No timeout specified.
7ce11014-2d7a-400a-b2c2-d9c7f5127b5d 2020-09-07 13:23:45.145091 [ERR] mod_dptools.c:2399 No timeout specified.

I subsequently worked out that the reason for the error was because the variable ${sleep} was not set. On newer installs I notice that sleep is set to 0 (zero) in Advanced->Variables. Should this new value have beed inserted into the vars table during the update process?

 

[Adrian Fretwell]

@markjcrane Please forgive me if I missed this in continuing education. I can narrow down the change happening between Jan 22 and Feb 17 this year but I have not been able to identify the commit with the "when and why" it was changed/added. Having the owner level of access to the repository, would you be able to find this out for me please? As you can see from the log extract above, it is causing errors on systems with older databases that have been upgraded.