Troubleshooting

Troubleshoot missing Quill replies and corporate network connectivity

Use this guide when Quill accepts a message but does not display a reply.

Quill does not show a reply

Quill uses a real-time connection to display responses as they are generated. A corporate firewall, proxy, or secure web gateway can block that connection while the rest of AirOps continues to work.

1. Refresh the page. If the reply appears after the refresh, Quill completed the request but the live update did not reach your browser.
2. Try Quill from another network and, if permitted, a device that is not managed by the same corporate security policy. A mobile hotspot alone may not bypass security software installed on your device.
3. If Quill works outside the corporate network or device policy, ask your IT team to allow the domains and protocols below.

Changing browsers, using a private browsing window, or switching networks may not help when security software on the device routes all traffic through the same corporate policy.

Corporate network requirements

Allow HTTPS and secure WebSocket traffic over TCP port 443 to these domains:

Domain	Protocol	Purpose
app.airops.com	HTTPS	AirOps and real-time channel authorization
ws-mt1.pusher.com	WSS	Primary real-time WebSocket connection
sockjs-mt1.pusher.com	HTTPS	XHR streaming and polling fallback
js.pusher.com	HTTPS	Fallback transport code

If your network policy supports wildcard domains, allow:

app.airops.com
*.pusher.com

The proxy must permit WebSocket upgrade requests and long-lived HTTPS connections used for XHR streaming. If TLS inspection disrupts these connections, exclude the Pusher domains from inspection.

Contact AirOps Support

If Quill still does not display replies on another network, contact AirOps Support. Include your workspace URL, browser, and the approximate time of the affected message.