I can reproduce. Trying to find out what happened.

@ahmedmfarahat Don't know how to fix the cloud yet, but here is a workaround...

Go to your IBM Cloud Resource list and find the Assistant service. Not the CF one that is just a link but the plain ol' service that it links to. (If you are unsure which one, then follow the app to the CF service and follow its link to the real service). Click on the real assistant service and you should see a Manage tab showing an API key and a URL. Copy those.

So the problem is that your CF app has a runtime environment variable (VCAP_SERVICES) with the wrong apikey. We can fix the app by adding the correct runtime environment variables with the following keys:

key: ASSISTANT_URL value:
key: ASSISTANT_APIKEY value

It should look something like this (w/ my specific values here cut-off) and the when you save both values the app should restart and just work :)

)

Yeah, but where can I change these keys found in the real service? please advice

I changed my WA credentials through cloud.ibm.com > resource list > your CF app > runtime environment, Added ASSISTANT_APIKEY AND ASSISTANT_URL and app restated automatically then worked perfectly. Thank you!