https://community.graphisoft.com/t5/Teamwork-BIMcloud/Joined-Unsent-Changes/m-p/187434#M3313 <BLOCKQUOTE>didrik wrote:<BR />More descriptive topic name than "erratic behavior." The behavior is pretty consistent for me. Opening a project that is used regularly, the status often shows as "Joined, Unsent changes." This occurs after sending and receiving, and after Release All and Send and Receive. I notice however, that Local Data Manager does not show unsent changes, so that may be an alternate way to check.</BLOCKQUOTE> This was brought up <A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=180834" target="_blank">here</A>. Although I have never had a problem with it myself, GS did mention that it is a bug that is due to be fixed. <BR /> <BLOCKQUOTE>didrik wrote:<BR />The false message makes <I></I><S><I><I></I></I></S>some<E></E> difference, if one wants to leave the project, since the report occurs that there are unsent changes. Also, it appears that one workstation will "know" that unsent changes are reported elsewhere, so there are then the messages about going to <I></I><S><I><I></I></I></S>the other<E></E> workstation (or user account) to send changes before Leaving the project at <I></I><S><I><I></I></I></S>this<E></E> workstation. Of course the user can override (ignore) the message, so the job gets done. It just requires fruitless checking to determine that the message <I></I><S><I><I></I></I></S>probably<E></E> is spurious.</BLOCKQUOTE> Would you mind uploading a screenshot of the message about going to the other workstation to send changes? I'm not sure I recall that one. <BR /> <BR /> Spurious - love that. <BR /> <BR /> Cheers,<BR /> Link. Wed, 09 Mar 2011 20:00:05 GMT Link 2011-03-09T20:00:05Z https://community.graphisoft.com/t5/Teamwork-BIMcloud/Joined-Unsent-Changes/m-p/187433#M3312 <DIV class="actalk-migrated-content"><R>More descriptive topic name than "erratic behavior." The behavior is pretty consistent for me. Opening a project that is used regularly, the status often shows as "Joined, Unsent changes." This occurs after sending and receiving, and after Release All and Send and Receive. I notice however, that Local Data Manager does not show unsent changes, so that may be an alternate way to check.<BR /> <BR /> The false message makes <I></I><S><I><I></I></I></S>some<E></E> difference, if one wants to leave the project, since the report occurs that there are unsent changes. Also, it appears that one workstation will "know" that unsent changes are reported elsewhere, so there are then the messages about going to <I></I><S><I><I></I></I></S>the other<E></E> workstation (or user account) to send changes before Leaving the project at <I></I><S><I><I></I></I></S>this<E></E> workstation. Of course the user can override (ignore) the message, so the job gets done. It just requires fruitless checking to determine that the message <I></I><S><I><I></I></I></S>probably<E></E> is spurious.</R></DIV> Wed, 09 Mar 2011 18:59:42 GMT https://community.graphisoft.com/t5/Teamwork-BIMcloud/Joined-Unsent-Changes/m-p/187433#M3312 Anonymous 2011-03-09T18:59:42Z https://community.graphisoft.com/t5/Teamwork-BIMcloud/Joined-Unsent-Changes/m-p/187434#M3313 <BLOCKQUOTE>didrik wrote:<BR />More descriptive topic name than "erratic behavior." The behavior is pretty consistent for me. Opening a project that is used regularly, the status often shows as "Joined, Unsent changes." This occurs after sending and receiving, and after Release All and Send and Receive. I notice however, that Local Data Manager does not show unsent changes, so that may be an alternate way to check.</BLOCKQUOTE> This was brought up <A href="http://archicad-talk.graphisoft.com/viewtopic.php?p=180834" target="_blank">here</A>. Although I have never had a problem with it myself, GS did mention that it is a bug that is due to be fixed. <BR /> <BLOCKQUOTE>didrik wrote:<BR />The false message makes <I></I><S><I><I></I></I></S>some<E></E> difference, if one wants to leave the project, since the report occurs that there are unsent changes. Also, it appears that one workstation will "know" that unsent changes are reported elsewhere, so there are then the messages about going to <I></I><S><I><I></I></I></S>the other<E></E> workstation (or user account) to send changes before Leaving the project at <I></I><S><I><I></I></I></S>this<E></E> workstation. Of course the user can override (ignore) the message, so the job gets done. It just requires fruitless checking to determine that the message <I></I><S><I><I></I></I></S>probably<E></E> is spurious.</BLOCKQUOTE> Would you mind uploading a screenshot of the message about going to the other workstation to send changes? I'm not sure I recall that one. <BR /> <BR /> Spurious - love that. <BR /> <BR /> Cheers,<BR /> Link. Wed, 09 Mar 2011 20:00:05 GMT https://community.graphisoft.com/t5/Teamwork-BIMcloud/Joined-Unsent-Changes/m-p/187434#M3313 Link 2011-03-09T20:00:05Z