Overview
When attempting to start a recording session in Architect, you may encounter a persistent loading state or an error message related to pending data. This typically indicates that Architect is unable to establish a connection with Functionize servers to transmit test data.
How It Works
Architect captures user actions on a web page and sends this information in real-time to a Functionize endpoint for processing. This requires a constant and stable network connection. If the data cannot be sent, it gets queued locally. When this queue reaches its maximum size, Architect will stop responding or display an error, as it cannot proceed without offloading the pending data.
Limitations
Architect's functionality is dependent on network access to Functionize services and may be limited by certain network configurations. It cannot operate correctly if the connection to its endpoints is blocked. This is a common issue in environments with strict firewalls, proxy servers, or certain VPN configurations.
To determine if you are affected by this limitation, you can perform a direct connectivity test:
- Open a new browser tab.
- Navigate to the following URL:
https://architect-stream.functionize.com/api/v2/ingest - Observe the result:
- Expected Result: A page that simply says "Bad Request". This indicates your connection is successful and not blocked.
- Problem Indicator: A browser error such as "This site can’t be reached" or a timeout message. This confirms that your network is blocking the connection.
Conclusion
If the connectivity test fails, the issue is related to your local network environment. You will need to contact your internal IT or network security team to have them allowlist or unblock access to the Functionize domains. While clearing browser cache and cookies is a good general practice, it will not resolve a network-level block.