Cannot Connect
Summary
Diagnose cases where Runline U cannot connect to the expected server or environment.
Symptoms
- Connection-oriented formulas return server or environment errors.
U.SUBSCRIBEorU.GETdoes not receive expected live data.- Administration/status formulas indicate no server connection.
Likely Causes
- The environment parameter does not identify a known environment.
- The local add-in is not authenticated or cannot reach the network/server.
- The workbook expects a different server or entity than the current user is configured for.
Step-by-Step Diagnosis
1. Check Environment
What to check: The environment input used by report formulas.
How to check: Inspect formulas with an environment parameter and compare them to known workbook examples.
Expected result: The environment is blank for main or a known configured environment.
2. Check Authentication
What to check: Whether the add-in has credentials for the environment.
How to check: Use existing admin/status formulas such as U.AUTHN, U.CONNECTED_TO_SERVER, or U.SERVER if present in the workbook.
Expected result: Status formulas indicate a usable authenticated connection.
3. Check Topic Scope
What to check: Whether the topic belongs to the expected entity/server.
How to check: Compare U.ENTITY, report group, report name, and server cells.
Expected result: The workbook addresses the same entity and server as the publisher.
Resolution
Correct the environment/server/authentication state before changing report formulas; formula edits will not fix a missing connection.