not sure but i am assuming nextcloud is not a polling remote. that would be seen in a rclone debug log.
in that case, 60m, rclone will only check for changes in the nextcloud remote every 60 minutes.
as a test,
- use
--dir-cache=1m - make a change in a file in nextcloud.
- wait one minute
- using a file browser, refresh it, to look for a change in the modtime of the file(s).
https://rclone.org/commands/rclone_mount/#vfs-directory-cache
note: there is a way to force rclone mount to update its local dir-cache to match nextcloud and not wait for --dir-cache-time to expire
i could be wrong but using --no-modtime might not be a good idea.