Question node keep on loading when user entered

I have given an input to the question node ,It’s keep on loading .
I checked the logs , where it facing an internal error in the platform.

{“level”:“error”,“f_t”:“2022-05-25T04:42:41.487Z”,“ist_timestamp”:“25 May 2022, 10:12:41 GMT+5:30”,“msg”:{“data”:"{\n “message”: “Request failed with status code 500”,\n “stack”: “Error: Request failed with status code 500\n at createError (/app/node_modules/axios/lib/core/createError.js:16:15)\n at settle (/app/node_modules/axios/lib/core/settle.js:17:12)\n at IncomingMessage.handleStreamEnd (/app/node_modules/axios/lib/adapters/http.js:260:11)\n at IncomingMessage.emit (events.js:412:35)\n at IncomingMessage.emit (domain.js:475:12)\n at endReadableNT (internal/streams/readable.js:1333:12)\n at processTicksAndRejections (internal/process/task_queues.js:82:21)\nFrom previous event:\n at httpAdapter (/app/node_modules/axios/lib/adapters/http.js:46:10)\n at dispatchRequest (/app/node_modules/axios/lib/core/dispatchRequest.js:52:10)\nFrom previous event:\n at Axios.request (/app/node_modules/axios/lib/core/Axios.js:61:23)\n at wrap (/app/node_modules/axios/lib/helpers/bind.js:9:15)\n at /app/models/ai.js:92:40\nFrom previous event:\n at AI.predict (/app/models/ai.js:90:16)\n at messagePredictor (/app/models/prediction/messagePredictor.js:33:42)\n at handlePrediction (/app/models/prediction/index.js:115:36)\n at /app/models/library.js:3186:62\nFrom previous event:\n at /app/models/library.js:3109:37\nFrom previous event:\n at checkContext (/app/models/library.js:3108:12)\n at /app/models/library.js:3848:112\nFrom previous event:\n at /app/models/library.js:3845:33\nFrom previous event:\n at App.start (/app/models/library.js:3”,“tag”:"Error in prediction api ",“sender”:“842539517028411599893167171”,“source”:“yellowmessenger”,“traceId”:“842539517028411599893167171_842539517028411599893167171_1r3LZQUxj6NcCQ5y4aXBS”},“botId”:“x1650273048873”}

Hey @pradeepkumaresan
There are 2 possibilities of why this is happening:

  1. Bot is not trained on at least 2 intents
    To resolve this, you just check if you’ve added 2 intents under NLU tab.

  2. Bot wasn’t operational for a long time (more than 24 hours)
    In this case, ping the bot multiple times (3-4 times) and it should work just fine.

If the issue persists, please feel free to share the bot ID and access with me at and I’ll have a look.