Connections can need attention even after they worked before. A provider may reject a request, a credential may have expired or been revoked, or a required permission may no longer be available. Start with the message the app actually shows. A failed connection request does not, by itself, explain where every asset is or what happened to every order.

Check the provider and connection name first. Then read the status and any error code or explanation. If the problem appears to be a temporary request failure, use the offered refresh or connection-check route deliberately and read its result. Repeating the same action rapidly does not create better evidence, and an older displayed balance should not be mistaken for a successful refresh.

If the issue concerns credentials or permissions, review the exchange's own access settings privately. Confirm that you are looking at the credential intended for TraderLobby. Do not post the key, secret, passphrase, or private key in a support request. A useful report names the affected provider, the action that failed, and a redacted message, without exposing the material that grants access.

The current connection screens do not provide a way to reveal and edit the saved secret. If replacement credentials are needed, follow the supported setup and removal workflow, and check the new result. Do not guess that changing a connection name updates the underlying key. The label and the access credential are different pieces of the connection.

Now distinguish removal inside TraderLobby from revocation at the exchange. Desktop offers Remove on the connection card. Mobile offers Delete and then a confirmation with Delete permanently. The mobile explanation says this removes the connection and its stored credentials. Do not assume the desktop button will give you the same extra confirmation; leave both untouched while following the lesson.

Removing the stored TraderLobby connection is not the same as revoking the API credential in the provider's account settings. If your intention is to revoke that credential, use the exchange's own access-management process as well and verify the result there. Do not assume that deleting the local connection makes a copied credential unusable everywhere else.

Removal also does not liquidate holdings, withdraw assets, cancel every outstanding order, or settle a subscription. If you intend to stop trading, handle the relevant automation, orders, and positions through their own workflows and confirm what happened. Losing the app's access can make managing an existing exchange position from TraderLobby harder; it does not make that position disappear.

There is one more context check after removal. If you remove the default connection, the current app can select another remaining valid connection as the default. Inspect the list afterward rather than assuming there is now no default. If no usable connection remains, read the resulting limitations. Do not create a replacement merely to clear a message while you are still investigating the problem.

For your check, explain how you would respond to a failed refresh, where you would review exchange permissions, and how local removal differs from provider revocation. Do not remove or revoke anything for practice. The result we want is a clear repair plan that protects access and keeps the account context understandable.