Hi,
first I want to thank to all of you who produced such an excellent ACS. 
I am using it in the production network for last 4 months and I didn’t get a single complaint from the field technicians regarding the provisioning of the devices or some other actions like status info check, reboot of FR actions that I exposed to them through the GUI that is using GenieACS NBI interface. And today is a small anniversary 500 (more precisely 501) devices on my instance of the GenieACS. 
I have one question. I prepared the script (actually GUI that runs that script) for the mass FW upgrade and I noticed something a bit strange. I want to explain briefly how my script works. Script first checks if the devices that are scheduled for FW upgrade are reachable (by using Connection Request) and if they are then the Download FW file action has been executed. If they are not reachable that action shouldn’t be executed. I wanted to test that logic so I first executed scheduled FW upgrade action (scheduled at 06:38) on one test device that was reachable and it went just fine:
2026-07-03T06:38:00.371Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: Inform; cpeRequestId=“1783060680_0915” informEvent=“6 CONNECTION REQUEST” informRetryCount=0
2026-07-03T06:38:00.403Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: ACS request; acsRequestId=“19f26b2cea70000” acsRequestName=“Download” acsRequestCommandKey=“19f26b2cea70000”
2026-07-03T06:40:07.838Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: Inform; cpeRequestId=“1234” informEvent=“1 BOOT” informRetryCount=0
2026-07-03T06:40:07.979Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: Inform; cpeRequestId=“1234” informEvent=“7 TRANSFER COMPLETE,M Download” informRetryCount=0
2026-07-03T06:40:08.009Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: CPE request; cpeRequestId=“2154” cpeRequestName=“TransferComplete” cpeRequestCommandKey=“19f26b2cea70000”
After that I scheduled another FW upgrade action (at 06:42) on the same device and in order to check what happens when that device is not reachable I sent it into the reboot 26 seconds before the scheduled FW upgrade action.
2026-07-03T06:41:34.449Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: Inform; cpeRequestId=“1234” informEvent=“6 CONNECTION REQUEST” informRetryCount=0
2026-07-03T06:41:34.484Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: ACS request; acsRequestId=“19f26b612e50000” acsRequestName=“Reboot”
The device was rebooted and it sent Inform message with the BOOT event some 57 sec. after the scheduled Download file action but then I saw that action was somehow executed 57 sec. after it has been scheduled, why? Does GenieACS wait some time with execution of some NBI actions for the devices that are currently not reachable? If yes, for how long does it wait?
2026-07-03T06:42:57.889Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: Inform; cpeRequestId=“1234” informEvent=“1 BOOT,M Reboot” informRetryCount=0
2026-07-03T06:42:57.910Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: ACS request; acsRequestId=“19f26b758da0000” acsRequestName=“Download” acsRequestCommandKey=“19f26b758da0000”
2026-07-03T06:45:16.322Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: Inform; cpeRequestId=“1783061115_0383” informEvent=“1 BOOT” informRetryCount=0
2026-07-03T06:45:16.440Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: Inform; cpeRequestId=“1783061116_0886” informEvent=“7 TRANSFER COMPLETE,M Download” informRetryCount=0
2026-07-03T06:45:16.477Z [INFO] ::ffff:100.100.1.146 503256-R281A-R2911251113001556: CPE request; cpeRequestId=“2154” cpeRequestName=“TransferComplete” cpeRequestCommandKey=“19f26b758da0000”
FW download action was executed successfully.
I am working now on the reporting part of the mass FW upgrade action and this situation complicates it for me a little bit.
Best regards,
Tarik