Switch to desktop version  
Logic of the scheduled action operation - Printable Version

+- Ewon Technical Forum (https://techforum.ewon.biz)
+-- Forum: Development (https://techforum.ewon.biz/forum-50.html)
+--- Forum: Ewon Embedded Technology (https://techforum.ewon.biz/forum-51.html)
+---- Forum: Ewon Core Features (https://techforum.ewon.biz/forum-3.html)
+---- Thread: Logic of the scheduled action operation (/thread-2820.html)



Logic of the scheduled action operation - mickaa - 16-01-2026

Hello,

I don't understand the logic behind how the 20 scheduled actions work. (Firmware 14.9 flexy 201/205)

The first 18 statuses are "Success" and only the last 2 statuses are "Full Queue".

1:FTP Put Success
2:FTP Put Success
3:FTP Put Success
[The same status: Success]
17:FTP Put Success
18:FTP Put Success
19:FTP Put Queue Full
20:FTP Put Queue Full

I thought the first 19 statuses would have to be at "-1 In progress" to have a "Queue Full" on the last status.


Could you please explain how the 20 scheduled action table works?


RE: Logic of the scheduled action operation - mickaa - 16-01-2026

(16-01-2026, 03:58 PM)mickaa Wrote: Hello,

I don't understand the logic behind how the 20 scheduled actions work. (Firmware 14.9 flexy 201/205)

The first 18 statuses are "Success" and only the last 2 statuses are "Full Queue".

1:FTP Put Success
2:FTP Put Success
3:FTP Put Success
[The same status: Success]
17:FTP Put Success
18:FTP Put Success
19:FTP Put Queue Full
20:FTP Put Queue Full

I thought the first 19 statuses would have to be at "-1 In progress" to have a "Queue Full" on the last status.


Could you please explain how the 20 scheduled action table works?

Everything's fine; the "Full" queue appears when the first 18 scheduled actions are in progress.
The script stops, and all processes have reached "Success."

I changed my mind; it makes sense.