Two days ago i tried the delayed detach function for one client. set a few projects that still had work to detach when work is done. But as soon as the client connected to BAM, it detached all projects immediatly with work still in progress, even those that were not marked to detach.

Today, i have trouble saving my preferences to projects, the link won't disappear no matter how long i wait or how often i click it.

Anyone else having these problems?

BAM ID: 36

for the host with the delayed detach problem
BAM Host ID: 46245
hostname: terra

and my preferences just saved, so i guess its solved or was only temp.

um... anyone looking into this?

i personally don't even care that much about this problem since i'll just do it manually to be save, but i guess someone else might try it and lose all his work...

Please do not post two entirely different problems into one thread (as is clearly stated in the bug submit guidelines)!

I tested the delayed detach, and it works as intended. Client versions prior to 5.10.x may have problems with this function, if you use an old version first upgrade.

The save to projects link disappears when *all* projects have been updated. If a project is down the link will stay.

There still seem to be problems in delayed detach. If I select a project for delayed detachment, save it and then select another project for delayed detachment, the previous project selected for delayed detachment enables new WUs again and the client disables detachment for it.

In order to work as intended, either all projects intended for delayed detachment are selected at once or BAM will corrupt the existing selections and only update the new one.

HTH

i should read more carefully... sorry...



i used client version 5.10.0. i will try again with 5.10.8 now, when my machines got the important work done.