Welcome @Pshre1
Hopefully we can help!
By this, do you mean that the job is queued (gray) or yellow (executing)?
Both are normal job states, especially for large, computationally expensive tools!
How this works: a Galaxy server is a sort of portal to computing clusters. At public Galaxy servers, those are large academic clusters that are processing your work and other people’s work. Some of your jobs run, some other jobs run, more of yours, repeat until completed.
The set of tools you are executing can take some time to complete! This is a recent topic where how to review a bit more for the resources used by this tool suite were explained.
Any of the UseGalaxy servers will work about the same as that example – and someone’s job completes at one of them every minute of every day! Very busy.
Until the job completes and comes back from the cluster node, there isn’t anything more to report about the status. What is known is on the job’s Details page (using the i-icon) and those are mostly metrics about how the job was set up – inputs, outputs, timestamps – not the data result or the logs generated during runtime. Most clusters work this way. Logs are returned when the job is returned. This is a bit different from running a tool locally on your same computer.
The good news is that later on, you can start using a workflow to speed things up! A workflow has all the jobs queued at the very start all at once, all of the parameters are pre-set (good for reproducibility), and notifications can be set for when it completes. This is how most working scientists are using Galaxy and other types of computing clusters, whether at their own cluster or ours.
I hope this helps and if I misunderstood, and instead you ended up with a job error (red dataset?) and you would like some help troubleshooting the problem, you are welcome to share your history back here and we can work through this with you. 