Well, engid talking abt the problem is not always good, but posting the solution might help someone if you face this issue in the future. so I contacted Yegra, and as always they are fast to respond. One of the best cloud providers that has the best customer service. so the problem exists and they already have the solution in their docs. Here is the link: https://yegara.com/en/guide/how-to-submit-a-process-kill-request/. Basically, what you do is add the &q=kill parameter to the URL after you log in to your account, and it will show you the process limit killing form request. You submit that, and they will kill it for you. If it's a VPS y'all Linux users know what we're gonna use ADELE ENDA 😁 it's in our blood

[ marc ] said that

#bugs_in_my_day Whether people understand or not, I like to talk about the issues I face and document them.

let me start with this, I have two Node.js processes running on my cPanel: an API and a background worker that syncs channel posts with my database

The worker is different from an API since you don’t send HTTPS requests to it. My mistake was clicking Run JS Script in the UI. That’s for APIs. For background workers/jobs, just save the details, go to the terminal, enter the project directory, and run the script in the background. Also, make sure to redirect the console output to a log file like app.log so you can check the worker’s health later. So yeah, if it’s not an API, use the terminal, not the UI button