ServiceException Sync failed
@kesselb is already working on this.
Since Oct 8, 2025.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
my gmail has been trying to sync for more than a year at this point. ive just let it be in the "loading messages state" to see if an update will fix it. the errors has changed slightly over time. i now get two slightly different ones:
ServiceException Sync failed for 2:[Gmail]/All Mail: IMAP message ID
https://paste.debian.net/hidden/9e7c3250/
ServiceException Sync failed for 2:INBOX: IMAP message ID
https://paste.debian.net/hidden/bd7f4c27/
Expected behavior
should just sync the mail from gmail.
Actual behavior
gets stuck on loading mail as described here: https://github.com/nextcloud/mail/issues/9102#issuecomment-2353465242
Mail app version
5.5.7
Nextcloud version
31.0.9
Mailserver or service
gmail
Operating system
lsio container: Operating System: Linux 6.8.0-85-generic x86_64
PHP engine version
Other
Nextcloud memory caching
No response
Web server
None
Database
MariaDB
Additional info
not sure if related or not:
https://github.com/nextcloud/mail/issues/9978
https://github.com/nextcloud/mail/issues/9102
PHP info:
Version: 8.4.11
Memory limit: -1 B
Max execution time: 3600
Upload max size: 100 GB
OPcache Revalidate Frequency: 60
Extensions: Core, date, libxml, pcre, zlib, filter, hash, json, random, readline, Reflection, SPL, session, cgi-fcgi, bcmath, bz2, ctype, curl, dom, fileinfo, ftp, gd, gmp, iconv, intl, ldap, mbstring, standard, pcntl, PDO, pgsql, posix, openssl, SimpleXML, sockets, sodium, sqlite3, sysvsem, xml, xmlwriter, zip, exif, mysqlnd, pdo_pgsql, pdo_sqlite, Phar, xmlreader, pdo_mysql, apcu, msgpack, igbinary, redis, memcached, imagick, imap, smbclient, libsmbclient, Zend OPcache
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.