the hourglass indicates a worker has not picked up the build yet. there are two possible reasons that this would happen:
no workers are available / are busy. when you configure drone (single-server) it will only run N concurrent builds. When you configure agents, each agent will only run N concurrent builds. If all workers are busy, the build sits in a pending state until a worker frees up
agents connectivity problems. A build can sit in a pending state when agents are misconfigured and cannot connect to the Drone server to pull builds from the queue.
@106062 please provide your full configuration (server and agent). Something looks wrong, because you do not provide the agent with DRONE_RPC_SERVER which would be required in order for an agent to connect with the server, which would in turn prevent builds from running.
Furthermore, it is also possible that you have configured your server to run in single-machine-mode (no agents) in which case mounting the volume into the server would be required.
Are you trying to run your server and agent on the same machine? If yes, you do not need an agent and should follow the single-machine setup instructions in the docs.
Not sure how can I fix this, but it looks like drone not able to send the status to agent. But surprisingly everything is perfect if we restart the build from UI, just happing for build triggered via webhook.