After updating a schedule, the web ui on the Schedules Preview page still shows the stale value.
Doing this with temporallite works great, but not on a cluster deployed in kubernetes.
After updating a schedule, the web ui on the Schedules Preview page still shows the stale value.
Doing this with temporallite works great, but not on a cluster deployed in kubernetes.
Hello @sebastian_violet
thank you for reporting this,
Could you share the code to reproduce the issue,
Thank you,
Antonio
This can be done directly on the Web UI also without using the Temporal SDK. Here is a Video of this: Dropbox - temporal-schedule-inconsistency.mov - Simplify your life
And the code equivalent is essentially:
ScheduleHandle sh = scheduleClient.getHandle(workflowId);
sh.update(
(ScheduleUpdateInput input) -> {
Schedule.Builder builder = Schedule.newBuilder(
input.getDescription().getSchedule());
//...
// change interval here
// ...
return new ScheduleUpdate(builder.build());
})
thank you for reporting this and for the video, it helps a lot.
Maybe there was an issue in UI version 2.16. I am not able to reproduce it with 2.19.
Are you able to upgrade the UI version?
Thank you,
Antonio
Hello @antonio.perez, I am deploying Temporal using the helm chart found here: GitHub - temporalio/helm-charts: Temporal Helm charts
I am using the latest version here; mainline. Is there perhaps a branch I should be using?
Also, when will there be a hosted Temporal repository?
Thank You
Should I manually update the value like so:
...
--set web.image.tag=2.19.0
...
Latest UI Server release:
Latest Web UI release:
Current default is here: https://github.com/temporalio/helm-charts/blob/41a3731c6e4121d3c587c775784e159ff1be2152/values.yaml#L321
Hi Sebastian,
I am wondering if the issues was in the server then, as I mentioned before I am not able to reproduce it.
Are your running this Temporal Helm charts with changing the UI version to 2.19.0?
Antonio
That is correct. And the latest server version.
It could be that the UI for the list page uses a different endpoint than the one used on the schedule full page; perhaps the former has the data cached and is stale, but the cache isn’t busted on update.