@Moors7 sorry i couldn’t reply earlier, but got some interesting results!
Logged in first thing, all my Cores were online which was great!
Tested the function of one of them, and after a slight wait, success! The function went through.
After which the Core went offline, my assumption why this happened was that after carrying out a function it looses connection so that your not able to spam the Core with functions.
After a little bit (<20sec) the Core back online, after refreshing your page, so I tried the same function with a different argument and the command JUST went through it seems (as I was writing this reply [maybe 1-2min?]!! That I was not expecting.
Is it possible to write an argument to an exposed function and have it kick in way after, after the Core is not blocking with user code? If the above is true, then this can work for my purposes, if it is not then how can I improve exposed function “responsiveness” ?
EDIT: Now I refreshed your page again, right after typing the above, to see if i can call the same Core again, and it went back offline. Even though it’s breathing cyan.