Bug 512682 - Calendar refreshes CalDav calendards too late
Summary: Calendar refreshes CalDav calendards too late
Status: REPORTED
Alias: None
Product: kontact
Classification: Applications
Component: calendar (other bugs)
Version First Reported In: 6.5.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-27 14:25 UTC by lagerimsi
Modified: 2025-11-27 16:03 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lagerimsi 2025-11-27 14:25:41 UTC
SUMMARY
Calendar refreshes CalDav calendards too late

STEPS TO REPRODUCE
1.  Add an appointment
2. try to search it before the normal update interval configured (default: 5 min.)


OBSERVED RESULT
The appoinment is not found in the search dialogue before the auto refresh timeout is reached or akonadi restartet (only appointments already synced to akonadi database are shown.

EXPECTED RESULT
find appointments immediately

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.17.9-arch1-1 (64-bit)
Graphics Platform: Wayland 

ADDITIONAL INFORMATION
My solution for now: refresh every minute. This produces 5x traffic on the server without changes; might be a problem with highly frequented servers.
A possible REAL solution: a second timeout to refresh the CalDav calendar after hitting the save button (30sec.). This prevents network problems to be a stopper while adding appointments.  The sync is done 30 sec. after the last entry saved. 
=> data in database and searchable
Comment 1 lagerimsi 2025-11-27 15:40:54 UTC
for exact understanding: "second timeout" behind  save button had to be reset every time hitting the save button
Comment 2 lagerimsi 2025-11-27 16:03:47 UTC
..logically better: reset the timeout with the start of adding/editing an event/appointment -> network problems would be avoided 

the solution in the comment above would leave a timegap of 30sec to add/edit an event. no good ;-)