Accessing your Network tab
This one is for the Chrome extension. When an order misbehaves, the log is the first place you look, and usually the last. But sometimes the log line is terse, or the exchange's error text is missing the detail you need. The exchange's full response often carries fields Autoview never surfaces because it isn't looking for them.
Because the extension runs on your machine, that raw traffic is on your machine too. Chrome's DevTools can show it to you, and support may ask you to open it when a case gets hard to read from the log alone.
Step 1: Open the extension's service worker
The extension's work happens in a background service worker, and that is where the network traffic lives. To inspect it:
- Go to
chrome://extensionsin Chrome. - Turn on Developer mode with the toggle in the top-right corner.
- Find the Autoview.com Trading Extension and click its service worker link.
A DevTools window opens, attached to the extension itself rather than to any web page. That distinction matters: DevTools on a TradingView tab shows you TradingView's traffic, not Autoview's.
Step 2: Open the Network tab and fire a test
In the DevTools window, click the Network tab. From now on it records every request the extension makes: what went to the exchange, and what the exchange sent back.
An empty Network tab tells you nothing, so make traffic happen. Set up a single-fire test alert for the command you're debugging; the testing and debugging guide shows how to build one you can trigger on demand. One note here: a command carrying d=1 never reaches the exchange, so a dry run produces log output but no exchange traffic. For the Network tab you need the real call.
When the alert fires, requests appear in the list. Click one. The response panel holds the exchange's full answer, and if you fired a position check, that answer is the exchange telling you, in its own words, everything it knows about the position you asked after. This is where you find the field the log never showed: the rejection reason, the precision limit, the flag on your account.
Small conveniences: the Escape key opens and closes the console drawer inside DevTools, and requests can be filtered by name if the list gets busy.
Two cautions
- Close DevTools when you're done. Recording everything costs memory, and the extension is a process you want lean. Open it to investigate, close it after.
- Never paste code into the Console tab. DevTools exposes the extension's internals, which is exactly why scammers ask victims to open it and run a snippet. Nobody legitimate, including Autoview support, will ever ask you to paste code there. Reading traffic is safe; running strangers' code is not.
Log first, Network tab second. Between the two you can see everything that passed between your machine and the exchange, which is the whole conversation there is.