Harshal Posted October 11, 2022 Report Share Posted October 11, 2022 Thank you all for your patience. We have discussed the possible solution with the backend team and get it in their backlog for them to prioritize and plan in their upcoming work. At this point, we believe that it won't require any new build for Immunet, It should be handled by applying the proposed fix in the backend. As the backend change will still require to be implemented, tested and deployed to the backend; I'll pass the information about ETA once I have it from the team. Thanks, Harshal 1 Link to comment Share on other sites More sharing options...
Milky Posted October 22, 2022 Author Report Share Posted October 22, 2022 Thanks Harshal! Link to comment Share on other sites More sharing options...
point5clue Posted October 23, 2022 Report Share Posted October 23, 2022 Am I missing something? Has there been an update since we had confirmation that “they are looking at it”? Link to comment Share on other sites More sharing options...
ritchie58 Posted October 24, 2022 Report Share Posted October 24, 2022 Hi guys, The dev team has had some time now to work on this issue. I'd like to see the fix implemented, or at the very least, I'm hoping Harshal will tell everyone that there is a definitive ETA when a fix will be rolled out, hopefully soon. "That's something I'd like to see happen too, just to put this issue to rest once & for all!" Best wishes, Ritchie... Link to comment Share on other sites More sharing options...
Harshal Posted March 28 Report Share Posted March 28 Hello all, Thank you all for your patience with this issue. Got an update from the backend team about the fix in place for the Immunet getting registered as Virus and threat protection product. Thanks again. Harshal Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now