temporalio / temporalio/temporal
[bug] Viewing schedule throws a 504 "context deadline exceeded"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
Expected behaviour is that I would be able to see the schedule
Actual Behavior
Out of the blue the schedules seem to be inaccessible, by which I mean the schedule page (for a single schedule, not the schedule list) throws a 504. Similarly I am unable to describe the schedule with the CLI:
$ temporal --env dev schedule describe -smy-schedule
time=2024-12-27T18:32:25.632 level=ERROR msg="context deadline exceeded"
I do not see anything in the error logs of the temporal server, I am using the auto-setup docker image. I have also noticed that this does not affect newly created schedules.
The schedules do not run anymore either.
Apart from that, the rest of temporal seems to be working properly
Steps to Reproduce the Problem
Not sure of the reproductability, the problem started on 1.25.1 seemingly randomly, upgrading it to 1.25.2 did not seem to change anything
Specifications
- Version: 1.25.1 & 1.25.2 with PostgreSQL 14
- Platform: linux amd64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing the failure through the schedule page and the CLI schedule describe command using the auto-setup image with PostgreSQL 14, comparing existing and newly created schedules across versions 1.25.1 and 1.25.2. Done means identifying the cause and restoring access and execution for affected schedules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100