# Query Completed Workflow

**URL:** <https://community.temporal.io/t/query-completed-workflow/3750>\
**Category:** Community Support\
**Tags:** go-sdk\
**Created:** [January 13, 2022, 3:24pm UTC](https://community.temporal.io/t/query-completed-workflow/3750 "2022-01-13T15:24:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonsve](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/jonsve/32/1626_2.png) [@jonsve](https://community.temporal.io/u/jonsve)\
**Post date:** [January 13, 2022, 3:24pm UTC](https://community.temporal.io/t/query-completed-workflow/3750/1 "2022-01-13T15:24:23Z")

</div>

According to the docs, a completed workflow will return its final result if queried

 ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/1/148a9c9e6ca205ca3702f90e971d079179ea0ac4.png)

We put our temporal cluster under a bit of load and a finished workflow answered with

“operation GetCurrentExecution encounter not found”

But now its answering fine

It says it can return either of these  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/7/7f3a3a17b64f184c1a165dfb5f56dfef9e5ecedf.png)

Did it actually return a EntityNotExistError ? Weird.

---

<div class="post-metadata">

**Author:** ![Chad\_Retz](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/chad_retz/32/1396_2.png) [@Chad\_Retz](https://community.temporal.io/u/Chad_Retz)\
**Post date:** [January 13, 2022, 4:31pm UTC](https://community.temporal.io/t/query-completed-workflow/3750/2 "2022-01-13T16:31:15Z")

</div>

> [@jonsve](#):
>
> It says it can return either of these

Which documentation are you seeing this? The list at [client package - go.temporal.io/sdk/client - Go Packages](https://pkg.go.dev/go.temporal.io/sdk/client#Client) for `QueryWorkflow` should be:

```auto
	// - serviceerror.InvalidArgument
	// - serviceerror.Internal
	// - serviceerror.Unavailable
	// - serviceerror.NotFound
	// - serviceerror.QueryFailed

```

> [@jonsve](#):
>
> Did it actually return a EntityNotExistError ? Weird.

The error can be checked for what type it is. Can you replicate this easily? A completed workflow should be queryable if it is otherwise available. Is the “completed” workflow potentially on a cron or scheduled for another execution via continue-as-new? There is a known issue querying a scheduled-but-not-started workflow.