Sporadically, you may encounter an error message which could not explain clearly what the issue is. We strive to have all errors with guided text indicating what are the steps to resolve the issue, but in some cases this error message may not contain any text, instead you will see just a code phrase.
When something like this happens, it will be a key point to encounter the error message from the code(when the error is coming from the API), make a screenshot and share it with our support team. This way we can act faster and find the issue in less time.
Structure of the article:
1. How to Open the Inspector from Your Web Browser
1.a Google Chrome
The easiest way to open the Chrome inspector is by right-clicking on the page, and then scroll to the bottom and click Inspect.
An alternative way will be by using a keyboard shortcut, open Developer Tools and bring focus to the console.
Windows: Ctrl + Shift + J.
Mac: Cmd + Option + J.
And here is the outcome:
Safari Web Inspector need two more additional steps before you can launch it and inspect the page:
Choose Safari > Preferences, and click Advanced.
At the bottom of the pane, select the “Show Develop menu in menu bar” checkbox.
At this point, you will now have an additional tab in the menu bar called Develop.
From there choose Develop > Show Web Inspector.
Windows: Ctrl + Shift + C
Mac: Cmd + Option + I
Firefox is very similar to Chrome when it comes to the part of using the Web Inspector.
Right-click any part of the page and choose Inspect.
From the Firefox top menu, select Tools > Browser Tools > Web Developer Tools
Windows: Control + Shift + C
Mac: Command + Option + C
2. Check for Errors in "Network" and "Console" Tabs
Once we have the Web Inspector open, we need to check first the Console tab for errors.
ℹ️ If you see error messages highlighted in red, make a screenshot of the entire browser window and continue to the Network tab.
When you open the Network tab, there is high probability that the tab is empty and there are no records, that is normal if you loaded the Web Inspector after the error appeared in your TIMIFY account.
Continue and select the Fetch/XHR option in the lower menus, and then in your TIMIFY account, repeat the same steps as you did before until the error message appears again.
You will then see records in the left sidebar under Name, and the one we are searching for is called
api.timify.io. Click on it and another line with options will open on the side.
Select Preview to see the data, and look for the one that says
errors, expand it and there will be a
message which will indicate where or what is the actual issue.
There could be a few
api.timify.ioidentical records, you will need to check which of them contains the
Not every error message in your TIMIFY account will generate
errorrecords in the Preview tab in the Web Inspector. This will happen only when the error comes from our API.