You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
The text was updated successfully, but these errors were encountered:
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: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 to1.25.2
did not seem to change anythingSpecifications
The text was updated successfully, but these errors were encountered: