2024-11-08
12:37 AM
- last edited on
2024-11-14
12:33 AM
by
Laszlo Nagy
here is a small sampling of the t/w warnings I have been trouble shooting the past week. This feels like something is broken... or theres something else at play here (my tinfoil hat is on pretty tight right now). And these are about 1/4-1/2 of what I've been sent:
2026-03-27 01:59 AM
moreover; poor teamwork peformance is a topic. I don't think it's worth posting a separate thread for each teamwork warning I get, when I get dozens per week.
crossing my fingers and toes this update/hotfix alleviates this issue
2026-03-27 07:13 AM - edited 2026-03-27 07:15 AM
Hi @Gordana Radonic,
thank you for reaching out to the comminity. I almost could not belive what I read this morning, after two years of fighting Graphisoft, of endless gaslighting, hold up tactics, and trying to blame the user, you not only admit one error, but mutliple on your end! That is awesome! For the first time I believe that there could be progress. 😀
But just to be sure that this is actually the official stance of Graphisoft and not some LLM generated halluzination (because your text is clearly written by LLM), could you once again please acknowlege:
there are currently mutliple bugs in the send & receive function that trigger this issue?
yesterday
like always, no follow up from Archicad 😀
But hey, why not give Graphisoft a fourteenth chance: Ping @Gordana Radonic
We had the issue again this morning, this time for all users.
Probably because something of teamserver crashed internally (no error in the webGUI, nor the desktop app) so we had to reboot the server. Of course that could be anything, since the warning is so generic.
yesterday - last edited yesterday
@jamesMorris Please start a new topic about the issue you mentioned.
Also, please report it to your local support/on the Support site (whichever applies in your country).
8 hours ago - last edited 8 hours ago
Am also encountering this issue recently when other members joined the teamwork. I noticed that if several users reserving certain settings like layers, profiles then it will hinder in sending, receiving or releasing unless that certain user release that certain setting on their end.
The other issue that I also encounter is that screenshot you provide (screenshot 2024-11-05 at 2.03.08PM (1).pdf) when I encounter this, it's like no hope... I restarted my system, delete all the things in the teamwork, discard the changes you did then and only it will work again... yeah what if you have done a lot of changes... save a copy and redo again... I hope that they can settle this issues...
--Just now writing this reply my archicad again encountered that issue... T_T
3 hours ago - last edited 3 hours ago
> @jamesMorris Please start a new topic about the issue you mentioned.
It is the same issue.
> Also, please report it to your local support/on the Support site (whichever applies in your country).
Why? For what? So that the first level support tells me to reboot the PC? I did and the issue got away. Are you interested in actually solving the root issue? Escalate it to second level to find out what was the root issue? Read some logs to hunt it down? Give me a ticket number?
I tried that for 3 years.
Only thing that did something was writing here. That embarassed Graphisoft Headquarters (as it should) and they pressured IDC Swiss to contact me. But what can they do? Despite telling me to reboot my PC? The only thing that could be done is that YOU guys finally think about how you can change your internal strucutres so that I am somehow as a paying support customers have a chance to escalate an issue.
But hey, that is all based on the assumption that someone is even interested in finding a solution. Not sure if that is really the case. Maybe Graphisoft thinks that the blast radius is currently too small and they don't care.