"Find a time" not beeing updated in time

[ericfischereu]

Steps to reproduce

1. Create an event in calendar of user A
2. As user B create a new event and and open the "Find a time" view.
3. User B is not able to see the blocker.
4. Reload the calendar and do the same again --> the blocker is there.

Expected behavior

Blocker events show up immediately after creation.

Actual behavior

Recently created events do not appear reliably in the "Find a time" view. After page reloads it works. In our case, there where 15-30min between the creation of the event and the panning of the second event.

Calendar app version

c.nc.c

CalDAV-clients used

none

Browser

Version 149.0.7827.103 (Offizieller Build) (arm64)

Client operating system

MacOS

Server operating system

No response

Web server

No response

Database engine version

No response

PHP engine version

No response

Nextcloud version

No response

Updated from an older installed version or fresh install

No response

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

No response

[odzhychko]

Behavior with shared calendars:

• User A shares calendar with User B
• User B opens /apps/calendar
• User A adds event X to calendar
• User B has to reload the page or User B has to wait around a minute see event X

Reproduced:

• after a minute the new event appears in the regular calendar view
• after a minute the new event does not appear in the "find a time" view

Probably we do not subscribed to changes from the server for the "find a time" view.
I think it's not a bug, but a use case, that was never specified.

[ericfischereu]

That behavior is kind of expected because Google and Microsoft handle it that way. The time span where events do not appear can be longer than a minute in reality. Also just to add the info the calendar does not have to be shared to appear in the Find a time view.

[ericfischereu]

@odzhychko It is probably a feature request - we noticed that the wrong user was invited originally. So indeed there could only be this one minute you discovered. I'd leave this open since I still think it's useful, but it isn't a bug.