Crawler / CX Model Known Issues
These were encountered over a single day of working with CX Models. For some of them, refreshing the page is the only workaround. For others, it's still not enough. I will be updating this list as more are encountered or fixed:
Running Confidence Score doesn't always pick up updated text. Have to run 2 or 3 times.
Playing the audio file sometimes doesn't play, and it just gets stuck at 0:00
Running multiple crawls at once produces crawler menus that are automatically verified
Verifying and updating a menu then clicking away will return it to unverified and with the old text. Then have to click and drag around for it to update.
Crawl Confidence Warnings don't do anything except bring you to the menu. Doesn't provide a recording of the bad audio or call.
Transcriptions assigned to a step after the initial one don't seem to pick up updated text, and just randomly add new ones.
Crawler doesn't pick up 1 2 3 4 etc. if they don't have press or say before it.
Doing a search, then updating one of the matched menus, makes the search go to 0 / 0 and you have to resubmit your search
Verifying a menu doesn't update its color in the Navigator. Even if you click and drag the red box around. You have to click and dragon around the main section.
The Crawls number is blank most of the time, even if there are crawls running. Same goes for the popup at the top.
Decision Elements throw a bunch of notification errors around missing scenarios when working with datasets, none of which are helpful or correct
The Confidence Score occasionally covers the Prompt label
The navigator moves more and more to the right, making it impossible to use the red box to the left side of the model
Clicking and dragging the slider in the Prompt(s) box drags the whole right panel up and down inversely
Visio export isn't correctly displayed in Visio viewer
Comments
17 comments
Thanks for this detailed post Christopher, I'll relay this feedback through to our engineering teams.
Happy to Daniel. I'll keep posting them here, likely other users are running into these.
Another one, the red box in the navigator gets locked up and won't let you click and drag it, requiring either a refresh or dragging the main section around to unlock it.
When deleting a menu, there is occasionally its response leftover just floating there by itself. Requires a refresh to disappear.
Sections of Models actively being worked on randomly disappear, requiring a refresh to reappear.
If your cursor is selected in the Prompt(s) text and you pause and play the audio, it moves the scroll of the prompt back to the top, making you lose your spot in a large prompt. Does not occur if your cursor is not select in the Prompt(s).
If running multiple crawls and you use a go-to while working on a separate section of the Model, you sometimes get a popup saying the menu has been modified or removed by someone else. Even though it hasn't, crawler isn't even working on either sections (the go-to or the menu to go-to), and it still works.
The popup when clicking the plus sign under a menu for the next element sometimes gets cut off if the plus sign is toward the top of the screen.
Pasting sections of CX Models sometimes errors with "Problems trying to copy Elements." This requires duplicating the entire model, there's no other workaround.
Hi Chris!
Thanks for sharing all this feedback. It is very important to have it publicly because it helps explaining these little things to other users.
At the same time I believe it is more of a support/dev case, and I will start converting your comments to Support tickets so we can address all these concerns in the next releases.
--
Valery
Thanks Val!
Definitely, I think others may have encountered these, and hopefully this post prevents duplicate tickets coming in.
Another one I found, if I refresh a model, and while the spinning loading wheel is occurring I click away to another application (Outlook, Excel, Notepad, etc. doesn't matter), and don't come back to Cyara for 30 minutes or so (until the timeout hits), Cyara goes into an infinite loading loop when I try to refresh. If I cancel the load in the browser, it brings me to the home page, where if I click on the CX Models > CX Models tab, that also goes into an infinite loop. I have to fully log out of the Portal and log back in to get it to stop.
Running into this, whose solution requires a support ticket to get fixed. Crawls sometimes "lock up" in the sense they get stuck and never finish and can't be aborted. If you go to Crawl History, you can see any and all models whose crawls are stuck. If you click Abort, the button goes grey upon the press, but the crawl doesn't actually abort and it just stays grey.
The transcriptions Crawler produces can have bad or inappropriate words in them. This becomes especially true if a foreign language is encountered.
It's being addressed with highest priority now. We are expecting the fix within next 1-2 months.
I found out how to consistently replicate this issue:
The Confidence Score occasionally covers the Prompt label
Click on any menu with a transcription, click on the Transcriptions tab. Click the main void whitespace to close the right side menu. Click the menu again (or any menu, doesn't matter) to re-open it, it should open on the Transcriptions tab. Click the Menu Details tab. Voila.
I found out how to replicate this issue:
The navigator moves more and more to the right, making it impossible to use the red box to the left side of the model
Click on the notification bell in the top right, click Verify Transcript for a menu that lives on the far left of the model. The Notifications popup will close, you will be brought to the menu, and the navigator will be pushed.
You can create the same effect in the other direction by clicking Verify Transcript for a menu on the far right.
Adding another one. Test Cases generated by CX Model, upon being added to a campaign and that campaign deleted, will still show the Linked Campaigns icon.
Just found this one today, there is no workaround. Reply steps in CX Model test cases don't pull the updates name.
To recreate:
Thanks Chris! I opened a support case to investigate the issue.
Please sign in to leave a comment.