I pulled the repo and did all that was described in https://temporal.talentlms.com/plus/my/training/126/units/2147 . Then I started doing this hands-on https://temporal.talentlms.com/plus/my/training/126/units/2121 . But when I run go run worker/main.go I get this error practice % go run worker/main.…

The error Unable to create client failed reaching server: context deadline exceeded tells us there’s no running or accessible Temporal server for the Worker code or CLI to communicate with. I’d dig into what exactly your Temporal server process is doing. What was the output when you ran the tempora…

Thank you. I get this CLI 1.5.1 (Server 1.29.1, UI 2.42.1) Server: localhost:7233 UI: http://localhost:8233 Metrics: http://localhost:51770/metrics Also, I ran the temporal server with temporal server start-dev --ui-port 8080 --db-filename cluster.db

Is the Temporal server running at the time you try running the Worker code? It seems like you might have run the server then cancelled/closed the process. You’ll need to run temporal server start-dev --ui-port 8080 --db-filename cluster.db in a separate window, and keep it open, to establish a serv…

No, I use two different terminals. The first for run the server and the second to run the workflow [Screenshot 2025-11-28 at 14.27.33] [Screenshot 2025-11-28 at 14.27.46]

I cloned the repo, made the single string modification indicated in your screenshot, and ran the code without any issues: [image] Is this a work computer, or a personal one? Does your workplace implement firewall or network security software on its endpoints that might stop services communicating…

Here are all the commands that were run. [Screenshot 2025-11-28 at 15.46.00] By the way, I can run temporal server start-dev --ui-port 8080 --db-filename cluster.db But when I try to run worker with go run worker/main.goI get an error Unable to create client failed reaching server: context dead…

I see that you ran cloud. Could you, please, move to ./exercises/hello-workflow/practice and run go run worker/main.go?

My examples were run locally from within the edu-101-go-code/exercises/hello-workflow/practice directory. context deadline exceeded is usually a network error. If you have a cloud address set in your environment variables (shown via the env | grep -i temporal), then you’ll need to unset that variab…

Troubles with hello-workflow in edu-101-go-code

Community Support

Illia_Sobko November 28, 2025, 12:41pm 7

It is just clear code from this repo GitHub - temporalio/edu-101-go-code: Code used in exercises and demonstrations for the "Temporal 101 with Go" course

The one thing that I changed is the name of the task queue name.

Topic		Replies	Views
Context deadline exceeded after upgrading go.temporal.io/sdk to version 1.27.0 Community Support go-sdk	0	392	July 14, 2024
Context deadline exceeded issue Community Support go-sdk	15	8314	November 20, 2024
Temporal error: context deadline exceeded Community Support go-sdk , server	1	1512	December 15, 2023
Context Deadline Exceeded error while executing workflow Community Support go-sdk	1	684	April 25, 2024
Trying to create new workflow after upgrading to v0.17.1. Seeing `context deadline exceeded` but no corresponding error logs in frontend container Community Support go-sdk	4	1396	July 16, 2022

Troubles with hello-workflow in edu-101-go-code

Related topics