-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WA starter kit: Watson discovery actions not loading #293
Comments
Yes, that kit is quite old, so it sounds like it needs to be updated. |
Thanks @jwm4 is there another place where I can find a working watson discovery action reference? also will this kit be updated any time soon to make it usable? |
I see that this kit hasn't been fixed in the past 3 months. I'm having this same problem and in my case it's to prepare a customer POC. Is there something I can do to help get this fixed? Or, as [yusufihmirza] asks, does anyone have an action skill integrated with Discovery that they can export and contribute? |
There is a more recent one in the second example here that also includes an integration with watsonx.ai to generate answers from search results. I don't know if that one works either, but since it is more recent, it might. If you don't want the integration with watsonx.ai, it should be pretty easy to start with that one and remove the watsonx.ai / answer generation stuff. |
Awesome! Thanks Bill! I'll switch to that repo and see how far I can go. The customer POC is intended to include a RAG summarization of the search results, so the watsonx.ai integration will be useful. |
So I installed watson discovery custom extension from starter kit here by import openAPI which went successfully. I added the instance with API key.
Then I was trying to load the actions from here to which I get the below error:
Error message:
Any idea why is it failing? I am using a new instance of Watson assistant from IBM techzone so assuming it is running on the latest version. Perhaps some issue with version compatibility?
Thanks!
The text was updated successfully, but these errors were encountered: