Welcome @Marcela_Davila
The public server are very busy right now for a training event (our yearly large global event), so jobs might queue a bit longer, especially a mapping job since these run on the largest clusters running the longest running jobs. Even if you query is small, the dataset itself is a bit of a memory hog, so it needs those cluster nodes!
So, the advice here is accurate and with maybe a bit more of a queue timing right now. This activity will settle out to normal over the next few weeks. Leaving your jobs queued is how to get them to process. Avoid deleting and rerunning since that new job will just enter the queue at the end again, extending the wait time.
If you still think there might be a problem, and want to share back your history, we can also double check that your job is set up correctly. How to share is in the banner topic, also here →
Hope this helps, and that your job completed by now, or will soon! 