You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to implode rooms which are part of a teams, This used to work earlier and we have used it. But now it seems to fail with the following error in the log
Potentially unhandled rejection [1] Error: Can not implode a 1:1 or Team room
Hi @dlsagayaraj this is in fact the designed behavior as bot.implode is designed to fail for 1-1 or teams rooms. TBH I'm not sure WHY it is designed to fail for a space that is part of a team, but I'm certain that has existed since the framework was first created as this appears to be leftover from the flint code that this framework is inherited from.
Are you certain this worked before (for spaces that were part of a team)? I'm dubious.
With that said, I'm not opposed to changing the framework to remove this limitation. As I said, I'm not sure why it was originally implemented that way. I've started a discussion about this in the "Webex Node Bot Framework" space on Webex if you'd like to comment more there.
In the meantime, here's a workaround (note that the promise will reject if the space is a 1-1 space (since Webex prevents these from being deleted, or if the room is moderated).
Thank you @jpjpjp , I will try this workaround. Btw, Yes i am sure this had been working earlier. I had been using this implode function to archive the unused spaces in a team. I have used it in 40+ spaces of the same team. Thanks for starting the discussion with the webex support team.
Unable to implode rooms which are part of a teams, This used to work earlier and we have used it. But now it seems to fail with the following error in the log
Potentially unhandled rejection [1] Error: Can not implode a 1:1 or Team room
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: