It’s not possible or favorable to keep waking a glitch bot up as it will self terminate and won’t listen until an actual web browser interacts with it.
It’s highly suggested to either pay for Glitch Pro for 24/7 running of your apps or use an alternative service as Glitch’s Policy on ‘keeping a full-stack app awake on a free plan’ isn’t allowed anymore.
I would probably suggest instead of kicking a player, keep the player ingame and have the server ping the glitch app over and over until it is successful, then to kick the player after it has ran.
Have a popup on the user screen stating that their rank is being updated, please wait.
Ping the glitch server over and over until it reply a “success”
Tell the client it has been finished, maybe show a green checkmark, “Good to go!”
Could even a few seconds before the user is intended to get ranked, ping the glitch bot to start waking up.
There is one other alternative if your glitch app’s simply won’t start in time.
Save all the data into Firestore Realtime Database or interface with a Roblox Datastore (nginx) module and have a server hosting locally on your own device that listens for new data and applys the rank itself.
Otherwise,
Could try self hosting and using ngrok if you are needing it for free.
I necessarily wouldn’t have a tutorial, but ngrok is quite simple.
If you know how to make a glitch app, find out how to move the glitch app to your own computer.
Once you finally get a page running the way you want on your computer, open an ngrok tunnel, and you’ll get an easy free http url right to your local server.
Hosting locally wouldn’t be a great idea for them. They would have to set up some scripts to keep it running 24/7 and I don’t think they’ll really want that.
Then there probably wouldn’t be a surefire way to ensure utmost reliability a while being free for something that requires constantly keeping a cookie alive for a Roblox Bot.
Only other ideas is seeing if response times improve on Heroku or repl.it