You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 5, 2021. It is now read-only.
Describe the bug
After importing a Botfront project using the import/export features of botfront, the "Incoming" > "New Utterances" tab stops populating data.
I've been able to bypass the problem in the test server by exporting data from botfront as Rasa files, and then likewise, importing them in as Rasa files.
To Reproduce
Steps to reproduce the behavior:
Follow the documentation to setup botfront on your local machine
Once botfronts running, train the model, and send a few messages to the bot to test it. The "New utterances" tab should be populating with records.
Go to settings > Import/Export > Export tab > Select export for Botfront > and export it. Toggling only the top option "Export project data".
Now import the same data back in as a botfront project.
At this point, the "Incoming" > "New Utterances" will no longer populate data. "Incoming" > "Conversations" will still populate conversations though.
My docker processes indicate I'm running: botfront:v0.27.5
The text was updated successfully, but these errors were encountered:
Describe the bug
After importing a Botfront project using the import/export features of botfront, the "Incoming" > "New Utterances" tab stops populating data.
I stumbled across this conversation which seems to match up with my issue.
https://spectrum.chat/botfront/help/new-issue-maybe-i-exported-a-json-from-0-27-1-and-upgraded-bf-to-0-27-2~12506b18-3092-48f0-b7cb-03c7713daa9d
I've been able to bypass the problem in the test server by exporting data from botfront as Rasa files, and then likewise, importing them in as Rasa files.
To Reproduce
Steps to reproduce the behavior:
My docker processes indicate I'm running: botfront:v0.27.5
The text was updated successfully, but these errors were encountered: