This is my first post here, although I’ve been using RocketChat and the forum as an observer for years. So please bear with me if I fail to follow any of the posting rules, ok?
In January my Workspace was automatically upgraded by the platform from Starter to the Professional version on a trial basis. After this period and when I returned to the Starter version (which suits me) because we only have 11 users, my Whatsapp Cloud application stopped working. I tried reconnecting, uninstalling, reconfiguring and it no longer worked. After reinstalling the app from the Rocket store, I couldn’t even connect it to Meta. So I decided to update my Workspace from 6.12 (6.13, 7.0 and finally 7.3). Even so, I can’t get it to work anymore, the message I get is:
“Sorry! Error occurred while saving Phone Number. Please try again.
More info: workspace service record does not have the Whatsapp service account enabled”
Hello.
I’m from Rocket.Chat support. We’ve seen a similar issue here. If you can provide me your workspace URL or cloud workspace ID I can manually enable from our side. You can DM me the information if you’d rather not have it public. This issue has been identified and our team is working to fix on future versions.
A decent report background report and some manners go a long way. Someone did their research first.
I’ll always try and help those who want to be helped.
A good report makes it easy to present to devs if we get stuck because it saves them a lot of their precious time.
But if you come here telling us you have a problem, provide little or no information, get aggressive when we ask for more, and then treat us like we don’t know what we are doing - when it is actually you with the problem, not us - you will get ignored.
Even worse will be the fact that we do know the issue, and how to fix it, but want to be absolutely certain with the facts first of all rather than vague guesses, because if we are wrong you will be on our backs.
Manually enabled your whatsapp cloud app, can you check again? If it doesn’t work right away, pls try clearing cache or restarting your server. Any further problems let me know.
Oh, and our dev team is aware of this issue, we’re tracking down what might trigger it. I’ll report it happened to you after switching plans, so it might be related to changes on License. Hopefully this is solved soon.
