Developer: There is no I in TEAM.
Tester: We can’t spell BUGS without U
Explanation of Bug Reports
At Telnyx, we're very much engineering focused. We're agile and iterate quickly, shipping improvements and new features regularly.
We're always grateful to our customers when it comes to identifying any and all improvements, especially bugs!
Let us know if you find any by contacting our support team by email email@example.com, we're always quick on hand to bring this feedback to the attention of our engineers, in order to ensure a better customer experience.
We always appreciate a detailed description of the bug, as well as any screenshots or videos you may have.
Security related bugs
If you have any security related bugs, why not email firstname.lastname@example.org who can discuss our bug bounty programme with you.
Don't forget! Our mission control portal user interface is built on top of our API, so check out your browsers console logs (front-end issues) or network logs (back-end issues) which can significantly help when it comes to reproducing your concerns.
Step by Step Guide:
Make sure to let us know what browser you are using and the version you are on.
Open the developer tools. In most browsers, you can do this by pressing F12 on your keyboard or by right-clicking on the page and selecting "Inspect" or "Inspect element" from the context menu.
Navigate to the website page you may have an issue with.
Once the developer tools are open, look for a tab labelled "Network" or "Console". Depending on your browser, this tab may be in a different location or have a different name, but it should be fairly easy to find.
For back-end issues click on the "Network" tab to inspect the network traffic for the page. You should see a list of requests that the browser made to load the page, including the URL, response code, and timing information.
You can save a HAR file by right clicking the request that's failing and clicking "save har file".
For front-end issues click on the "Console" tab to inspect the console logs for the page. This is where developers often log messages and errors for debugging purposes. You can filter the logs by type, such as "Errors" or "Warnings".
If you see any red logs you can right click the whitespace and save the console logs.
These files will be very useful to determine the cause!
If the bug is mission critical (service affecting), please open a chat with ourselves in support and we will investigate it immediately.
Can't find what you're looking for? Click the chat bubble at your lower right-hand corner and talk to the support team!