Agree that it seems to be on complicated pipelines. One thing I have figured out that 'sort' of helps is:
As soon as you see an error flash up on the top right (Offline, Internal Error, etc), just stop right then. Anything you do past that point will not be saved and will screw things up. What I wrote in my original post "If I wait 10 minutes it seems OK" is NOT true.
For example: I just had a a long pipeline. In the middle of the pipeline I got an error message. I kept going and when I finished, it wouldn't let me click out (gave me the 'you will lose any unsaved changes' message). Nor would it let me turn on the pipeline. I let it sit there for 10 or 15 minutes and boom, it seemed great.
However, if I left and came back in, everything I did AFTER that error message was totally wonky. Some was gone, some was just plain wrong.
I rebuilt the pipeline, and this time kept turning on the pipeline and made sure it would turn on properly. If it did, I continued. If it didn't, I immediately backed out and came back in and continued. I was able to build the entire pipeline.
Obviously, this is not remotely ideal. BUT, if you have a complicated pipeline, it might save you the nightmare that I have been through of rebuilding over and over. Essentially, make small changes. And if its really complicated, copy it before you make any changes.
Also, I can't import/export or it gives me the internal error.
Overall, like you said I really want Pipelines to be good but it's pretty rocked with bugs right now to utilize it.
------------------------------
Mike Tamoush
------------------------------