How do I report bugs

Encountered a bug? Find out how to provide all the essential information for speedy resolution.

Bugs should be reported by sending an email to support@askuma.ai or from our portal.

In order to get the best help possible, please provide as much context on how you encountered the bug.

Generate Network Captures for Troubleshooting

HARA HAR capture (HTTP Archives) records the requests and responses that your browser makes within UMA.

In Chrome, go to the page within UMA where you are experiencing trouble.
At the top-right of your browser window, click the Chrome menu (⋮).
Select tools > developer tools. The developer tools window opens as a docked panel at the side or bottom of Chrome.
Click the network tab.
Select preserve log.
You will see a red circle at the top left of the Network tab. This means the capture has started. If the circle is black, click the black circle to start recording activity in your browser.
Refresh the page and reproduce the problem while the capture is running.
After you successfully reproduce the issue, right click on any row of the activity pane and select Save as HAR with content.
Select the console tab
Right-click anywhere in the console and select save as....
Name the log file Chrome-console.log.
Send both files as shared links in a reply to your case.

In Firefox, go to the page within UMA where you are experiencing trouble.
Click the Firefox menu (Three horizontal parallel lines) at the top-right of your browser window.
Select web developer > network.
The developer tools window opens as a docked panel at the side or bottom of Firefox.
Click the network tab.
Select persist logs.
Refresh the page and reproduce the problem while the capture is running.
After you successfully reproduce the issue, right-click any row of the activity pane and select Save all as HAR.
Select the console tab.
Right-click any row and select select all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.

In Safari, go to the page within UMA where you are experiencing trouble.
In the menu bar at the top, click develop and select show web inspector.
Click the console tab and select preserve log.
Go back to the network tab.
Refresh the page and reproduce the problem while the capture is running.
After you successfully reproduce the issue, right-click any row of the activity pane and select export HAR.
Click the console tab.
Right-click any row and select select all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.

In Internet Explorer, go to the page within UMA where you are experiencing trouble.
Click the gear icon in the top right.
Select F12 developer tools.
Click the network tab.
Clear the clear entries on navigate option, which is selected by default. The icon looks like blue arrow with a red X.
The green play button (start profiling session), should be selected by default. This means the capture function is running.
Refresh the the page and reproduce the problem while the capture is running.
Once you have reproduced the issue, click the export as HAR icon. The icon looks like a floppy disk.
Click the console tab.
Right-click any row and select copy all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.

In Edge, go to the page within UMA where you are experiencing trouble.
At the top-right of your browser window, click the Edge menu (⋮)
Select developer tools.
Click the network tab.
Clear the clear entries on navigate option, which is selected by default. The icon looks like blue arrow with a red X.
The green play button (start profiling session), should be selected by default. This means the capture function is running.
Refresh the the page and reproduce the problem while the capture is running.
Once you have reproduced the issue, click the export as HAR icon. The icon looks like a floppy disk.
Click the console tab.
Right-click any row and select copy all.
Paste the content in a text file and name it console-log.txt.
Send both files as shared links in a reply to your case.

Last updated 6 months ago