Hi @Pradip007,

This is expected in the free edition. In the free edition, your queries run on a shared regional serverless pool with a small effective warehouse capacity and best-effort access. Even if you’re the only user in your workspace, you’re sharing the underlying pool with other workspaces in the same region, with strong isolation at the warehouse/session level. The behaviour is normal from a query that spent most of its life waiting for serverless capacity, which you can confirm by checking waiting_at_capacity_duration_ms in system.query.history and correlating with system.compute.warehouse_events around that time.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.