Sachin Verma

We are also facing same issue with Grails 3.3.9. We had to change from lazy:'false' to fetch:'join'. Any update on the issue?

@catch-n-release I have checked. it doesn't work if already schedule exist in the current code as it hits only schedule api not reschedule api. It fails. Due to this i...

@pallupz Sure and thanks i will check that cancel option as well.

@pallupz thanks. Now, I am able to cancel the slot from cowin. Yeah its not intuitive for cancel and also from Arogya Setu app on cancelling it was giving API...

@pallupz No i was trying for first dose only just i didn't cancel existing appointments only. One of the appointment was of past date.

@pallupz I didn't see any code of reschedule for already existing appointments. How it was using reschedule if appointment already exists? @catch-n-release I was trying on 19th May.

@benfortuna when it would be fixed in ical4j? We too got hitdown yesterday with the same issue as there was DST change -04:00 to -05:00? Is there any alternate available...

Any solution on this?

@mukeshkamboj Reason.. is RedisSession data not accessible so for secured URLS no session data available to validate thats why 401 as User is not logged in due to missing redis...

> https://github.com/grails/grails-spring-security-rest/pull/521 will bring this back to life for grails 6.1.1+. We plan to also update this plugin for Grails 7. Thanks @jdaugherty that will be great.