# Show query progress, specifically for long running queries

**URL:** <https://discuss.dgraph.io/t/show-query-progress-specifically-for-long-running-queries/8446>\
**Category:** Dgraph\
**Tags:** dgraph, kind:enhancement, area:querylang, exp:expert\
**Created:** [August 23, 2019, 5:47pm UTC](https://discuss.dgraph.io/t/show-query-progress-specifically-for-long-running-queries/8446 "2019-08-23T17:47:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![diggy](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/diggy/32/3666_2.png) [@diggy](https://discuss.dgraph.io/u/diggy)\
**Post date:** [August 23, 2019, 5:47pm UTC](https://discuss.dgraph.io/t/show-query-progress-specifically-for-long-running-queries/8446/1 "2019-08-23T17:47:18Z")

</div>

**Moved from GitHub [dgraph/3857](https://github.com/dgraph-io/dgraph/issues/3857)**

_Posted by_ [MichelDiz](https://github.com/MichelDiz):

### What you wanted to do

A massive upsert (milions of nodes).

### Why that wasn’t great, with examples

All massive upserts take some time to execute. The massive upsert works fine, but there’s no visual reference during the process if it is going well or not. Sometimes Ratel could fail visually or the Browser (for some reason) and We’re not sure if the Big Upsert was executed or still executing.

We could have two types of reference for this. Could be API responses (if possible) sending percentage values and a log in the Alpha’s log terminal. The log would start to appear only if the transaction takes more time than usual.

### Observation

This probably would be done after we have a Query Planner.