Unable to get workflow details in temporal UI http://localhost:8088/

Community Support
1

seeing the following error message and the workflow details are not shown

details: 'GetWorkflowExecution failed. Error: not found ’ }
temporal-web_1 | { Error: 5 NOT_FOUND: GetWorkflowExecution failed. Error: not found
temporal-web_1 | at Object.exports.createStatusError (/usr/app/node_modules/grpc/src/common.js:91:15)
temporal-web_1 | at Object.onReceiveStatus (/usr/app/node_modules/grpc/src/client_interceptors.js:1209:28)
temporal-web_1 | at InterceptingListener._callNext (/usr/app/node_modules/grpc/src/client_interceptors.js:568:42)
temporal-web_1 | at InterceptingListener.onReceiveStatus (/usr/app/node_modules/grpc/src/client_interceptors.js:618:8)
temporal-web_1 | at callback (/usr/app/node_modules/grpc/src/client_interceptors.js:847:24)

2

server version 0.28.0

3

@kasi thanks for opening the issue!
Could you provide more details on how to reproduce the issue
Are you trying to navigate to a workflow from /workflows page by clicking on one of them?
Are you able to find the same workflow from tctl command line? ie. tctl --ns default wf describe -wid <workflow_id> -rid <run_id>

5

Hi Ruslan,

Yes I am trying to navigate to a workflow from /workflows page by clicking on one of them.
./tctl --ns sample-namespace wf describe -wid f0fec172-f2d6-48e9-9281-4ab84fb00814 -rid 9afa0eab-4682-4a09-a59a-156c7d1443ea
Error: Describe workflow execution failed
Error Details: GetWorkflowExecution failed. Error: not found
Stack trace:
goroutine 1 [running]:
runtime/debug.Stack(0xd, 0x0, 0x0)
/usr/local/go/src/runtime/debug/stack.go:24 +0x9d
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
go.temporal.io/server/tools/cli.printError(0x28c98ea, 0x22, 0x2c769c0, 0xc0004d0180)
/Users/user1/temporal/tools/cli/util.go:530 +0x2ad
go.temporal.io/server/tools/cli.ErrorAndExit(0x28c98ea, 0x22, 0x2c769c0, 0xc0004d0180)
/Users/user1/temporal/tools/cli/util.go:541 +0x49
go.temporal.io/server/tools/cli.describeWorkflowHelper(0xc00096a160, 0x7ffeefbffc89, 0x24, 0x7ffeefbffcb3, 0x24)
/Users/user1/temporal/tools/cli/workflowCommands.go:851 +0x35f
go.temporal.io/server/tools/cli.DescribeWorkflow(0xc00096a160)
/Users/user1/temporal/tools/cli/workflowCommands.go:816 +0xa5
go.temporal.io/server/tools/cli.newWorkflowCommands.func15(0xc00096a160)
/Users/user1/temporal/tools/cli/workflow.go:197 +0x2b
github.com/urfave/cli.HandleAction(0x252de80, 0x2936808, 0xc00096a160, 0xc00096a160, 0x0)
/Users/user1/go/pkg/mod/github.com/urfave/cli@v1.22.4/app.go:528 +0x7c
github.com/urfave/cli.Command.Run(0x289682d, 0x8, 0x0, 0x0, 0xc000862dd0, 0x1, 0x1, 0x28d5bb9, 0x26, 0x0, …)
/Users/user1/go/pkg/mod/github.com/urfave/cli@v1.22.4/command.go:174 +0x57a
github.com/urfave/cli.(*App).RunAsSubcommand(0xc00045ddc0, 0xc0000c58c0, 0x0, 0x0)
/Users/user1/go/pkg/mod/github.com/urfave/cli@v1.22.4/app.go:407 +0x915
github.com/urfave/cli.Command.startApp(0x2897155, 0x8, 0x0, 0x0, 0xc0008630b0, 0x1, 0x1, 0x28b444a, 0x19, 0x0, …)
/Users/user1/go/pkg/mod/github.com/urfave/cli@v1.22.4/command.go:373 +0x845
github.com/urfave/cli.Command.Run(0x2897155, 0x8, 0x0, 0x0, 0xc0008630b0, 0x1, 0x1, 0x28b444a, 0x19, 0x0, …)
/Users/user1/go/pkg/mod/github.com/urfave/cli@v1.22.4/command.go:102 +0xa2b
github.com/urfave/cli.(*App).Run(0xc00045da40, 0xc00003c090, 0x9, 0x9, 0x0, 0x0)
/Users/user1/go/pkg/mod/github.com/urfave/cli@v1.22.4/app.go:279 +0x7c7
main.main()
/Users/user1/temporal/cmd/tools/cli/main.go:37 +0x4b

6

Does this happen with a specific workflow execution, or just any? Do navigation/describe command work with other workflow executions?
Is this default configuration with Cassandra? Are you running using docker-compose?

7

It happens with the workflow created in custom namespace, simple workflow with default namespace seems to be working, running with docker-compose

8

@kasi

When you create a namespace, could you validate that the retention period is not set to zero days.

tctl --ns <namespace_name> namespace register --retention <retention_in_days>

from tctl namespace register -h:

–retention value, --rd value Workflow execution retention in days

9

Hi Rusian,

Thanks a lot, that was the problem.

Kasi

1 Like
10

This topic was automatically closed after 34 hours. New replies are no longer allowed.