Dear community members,
I want to start by genuinely acknowledging the frustration many of you are experiencing with Teamwork warning messages that don't clearly point to the source of a problem. We are well aware that these issues are affecting your daily work, and I am truly sorry you are going through this. As a couple of members before me have noted, this is not the level of support experience we want you to have, and your feedback matters to us.
I'd also like to say, as a member of the community team, how much I value seeing this community come together, even in threads born out of frustration. Peer help is at the heart of what makes this space valuable.
I'd like to offer a few points that I hope will help community here:
Teamwork and BIMcloud issues are highly project-specific. Because the root causes can vary significantly from project to project, the fastest and most effective path to resolution is through your designated technical support - whether local or direct. Our support team regularly investigates files and support packages related to BIMcloud and Teamwork, and that is where these issues can be properly traced and resolved.
Our recommendations:
1. Always report Teamwork and BIMcloud issues to support - whether through your local partner or directly via the Graphisoft Support site. To help your support engineer investigate as efficiently as possible, make sure you have the following ready when submitting:
- Archicad version and build number
- Operating system and hardware specifications
- Detailed description of the problem
- Steps to reproduce the issue
- Screenshots, videos, or error logs (max attachment size: 50 MB)
It is also very likely that your designated support engineer will ask you to create a Support Package — you can get familiar with that process here: Creating a Support Package.
2. Keep one thread per topic. This helps both peers and our team follow the issue, contribute meaningfully, and track progress - and it is in line with our community guidelines.
I also want to take a moment to specifically acknowledge @Patrick M — despite the persistence and difficulty of the issues he and his team are facing, and many of his posts here, his collaboration with our technical support team has been exemplary. This is exactly the kind of engagement that leads to real resolutions, and I hope it encourages others to do the same.
On a positive note, I am pleased to share that Archicad 29.1.0 has just been released today, and it includes improvements that are directly relevant to the issues raised in this thread. Specifically, it addresses a significant number of the causes behind the Send & Receive errors many of you have been experiencing. From your perspective, these errors often appeared as random, unexplained failures that blocked you from continuing your work — with no clear indication of what went wrong. The reality is that these errors could stem from several different underlying causes, and with this update, we hope that most of those known causes have now been resolved.
One concrete example of what has been fixed: we implemented a fix that prevents duplicated layer combination settings, which could cause issues with Teamwork Send & Receive (DEF-26691).
That said, we want to be transparent: because the general Send & Receive error message can be triggered by a wide range of factors, some yet-to-be-identified causes may still surface — and if they do, please report them to so they can be properly investigated.
You are able to download the update and check the release notes here: Archicad 29.1.0 page. We have also announced it as usual in Graphisoft Insights: What's new in Archicad and MEP Designer?
Going forward, I kindly ask that new technical questions be posted as their own threads. This is not about discouraging conversation and discussions — quite the opposite. Focused threads are easier to follow, easier to search, and much more likely to get the right eyes on the right problem. Thank you for helping us keep the community organized and useful for everyone.
We hear you, and we are working on it.
Gordana
Gordana Radonić
Community Manager
Laszlo Nagy
