Behavior change on the service edit: Recording link:Password: yFpC4BuiI see a behavior change on the service edit.I have created a ODN policy successfully.Then I moved the device to out of sync with NSOAfter that I edited the service and both NSO UI and CAT are showing that the service is in successful state.NSO cli shows that the service is in failed state. See the below output.Now when the user re-deploy the service then NSO and CNC UI get updated that the services are in failed state.The expectation is when I edited the service at the first place the failure from NSO should have propagated to CAT.The service shows a failure only when the user re-deploy it.See the attached plan failed.
 Hi Joby,Thank you very much for raising JSD ticket .With no-CQ service update commit failure, there is nothing on NSO or device that has changed so plan state doesnt change.As we have seen with CQ we have not seen this issue .There is one platform ticket already raised for similar issue.For Non CQ what you currently see is by design .Thanks,Priyanka