Capturing Detailed Errors
Show Error Log
If you encounter an issue in Workamajig where things just do not seem right, please let us know. But in addition to letting us know, and if you are logged into your account. Then click on your name in the upper right, then go to More > Show The Error Log.
If there was an issue in your current instance, then you may see something like this drop down.
Feel free to send us a screenshot of it or copy the text and paste it into your email to support@workamajig.com.
Advanced Tools
For even more details on the error, if it something you can reproduce, you or your IT folks can try the following.
NOTE: If you are hosted on your own server and that server is behind a firewall that Workamajig support cannot access, then here are some steps that your IT can run through in capturing more detailed info about your issue.
From Chrome
The following steps work ion a Windows or Mac using the Chrome browser.
NOTE: This method of using the browsers developer tools is tab specific. So if you click a link that pops open another tab/page, then you will need to "inspect" that tab/page separately.
1. Open the Developer Tools
Press “Ctrl+Shift+I“, or Right-Click anywhere and choose “Inspect”, or click the “three lines” > More Tools > Developer Tools.
2. Enable Pause On Caught Exceptions
Click on Sources, and check Pause On Caught Exceptions.
3. Reproduce the Issue
Then go back to Platinum and reproduce the issue. At which point the dev screen should open up to a blue line where the code stopped working.
4. Take a FULL screenshot
Take a screenshot of the blue line or copy and paste it, noting the line number.
NOTE: You can also right-click on the Console section and choose Save As to output the entire log using a ".txt" file name. The Console section can also detail transfer times to see if there are performance issues at the server or on your network.
5. Send your details to support@workamajig.com.
Send all related files and detailed steps to Workamajig Support via email at support@workamajig.com.
Comments
0 comments
Article is closed for comments.