Chat bot training taking long time to confirm - training in progress

  • Hi There,

    I have uploaded information to the chatbot training. However its say”Training in progress” which is taking almots 2 days to confirm. I have uploaded information before and it took about 30secs? Not sure what has chanaged or why its taking so long to confirm?

    Apprececiate your help

1 Like

Same. AI ChatBot is pretty much not answering any questions. It’s asking users to send an email. This was working flawlessly. I did not make any changes. It just stopped answering the questions as it’s done numerous times before. Also, stuck in training mode.

Hi @Michael_Paulse and @StripClub_Reservatio! Welcome to whe Community :waving_hand:

The thing is, we were having trouble with the AI Chatbot training recently. The root cause was the issue on the AI provider side.

Because of the issue, the training process got stuck, and you might have seen see the following identifiers in your widget settings:

To have your bot trained with that info, you will need to delete that pending information and add it again.

Please let me know how the things go, and I’ll be glad to assist further if needed :folded_hands:

UPDATE: nothing is working in terms of getting the AI chatbot to answer the question with the provided answer that contains a url.

Also, I deleted the Q&A that is stuck in “training”, and added it again. While it removed the “training”, it did not fix the issue of not giving the provided answer.

Still having issues now going on over a week. AI Chat is not giving the provided answer on “how do I make a reservation?” it used to, not any more. I’ve deleted and added it again. FYI, the answer contains a url.

https://hunkmansion.com/

Hello, @StripClub_Reservatio!

Thank you for the details, and let’s figure it our together :folded_hands:

I just tried asking your Chatbot the question from your example, and it seems to have answered fine:

I also reviewed your instruction and Q&As, and it looks like they don’t have any major mistakes there.

Could you please share if the error is still present? If so, provide me with a screenshot, and our dev team will take a closer look :raising_hands: