Forum Discussion
BUG::PIPELINE::TEAMS ACTIVITY::SETTINGS NOT SAVED
- 2 years ago
So here is what happened now... I opened the pipeline again and upon clicking on each Teams activity and navigating to the settings, all the settings showed up as set yesterday.
Then I did this. I clicked on a Teams activity in the same pipeline that was copy/pasted from another pipeline (and that pipeline what copy/pasted from another workspace--I forgot to mention this yesterday). So, when I click on this Teams activity, none of the settings show up as they are in that other workspace pipeline. That's fine.
But then, if I click back on the Teams activity that was created within the pipeline I am currently working on, and whose settings just showed up as I had set them yesterday, now they show up as not set, like this:
So I think this is a client Javascript issue. Because like I said above, when I re-opened the pipeline today, the settings were all there as when I had set them yesterday. And now, after switching the focus back and forth between 2 Team activities (one natively created within the current pipeline, and one copy/pasted from another pipeline from another worskpace)) the settings appear gone again. I suspect after I save the pipeline, close it, and re-open it later, the settings will show as set properly again.
Hey Element115
Even I do not log out from Fabric. It has been logged in from Day 1. I never logged out.
Please try again and let me know.
So here is what happened now... I opened the pipeline again and upon clicking on each Teams activity and navigating to the settings, all the settings showed up as set yesterday.
Then I did this. I clicked on a Teams activity in the same pipeline that was copy/pasted from another pipeline (and that pipeline what copy/pasted from another workspace--I forgot to mention this yesterday). So, when I click on this Teams activity, none of the settings show up as they are in that other workspace pipeline. That's fine.
But then, if I click back on the Teams activity that was created within the pipeline I am currently working on, and whose settings just showed up as I had set them yesterday, now they show up as not set, like this:
So I think this is a client Javascript issue. Because like I said above, when I re-opened the pipeline today, the settings were all there as when I had set them yesterday. And now, after switching the focus back and forth between 2 Team activities (one natively created within the current pipeline, and one copy/pasted from another pipeline from another worskpace)) the settings appear gone again. I suspect after I save the pipeline, close it, and re-open it later, the settings will show as set properly again.
- Anonymous2 years agoNot applicable
Hi Element115
Thanks for the feedback. I have informed the internal team regarding this. If this is a bug, we will definitely fix it. But I couldnt find any issue at my side when I did the repro.
Thanks- Element1152 years ago
Memorable Member
I don't know if I mentioned it, but yesterday I also started using multiple Edge profiles concurrently. It shouldn't matter, but if it is a client/Javascript issue, perhaps there's a connection.