# Manage service connections

Control application-specific observation without reinstalling an existing SDK.

## Connect a service

Connect an existing service to the application. If its SDK is already installed, retain the service identity. Observation for the additional application can begin after its valid signed scope reaches the service. A portal connection alone cannot instrument a service that has no SDK.

## Disconnect from one application

Use the application’s disconnect action rather than cancelling the entire service definition. Other applications’ active connections remain in effect. A service outside the valid observation scope does not record its own steps; supported propagation can still carry the actual context to a downstream service.

## When changes take effect

SDK profiles refresh in the background; the current normal interval is 30 seconds. A verified updated profile applies to new executions. Executions already in progress retain the service scope fixed at their start, preserving consistent application attribution.

## Reconnect a service

Reconnect the service and start a new transaction. An installed SDK does not need to be reinstalled, but service identity, trust configuration and actual context propagation must still be correct. Verify receipt in the transaction list and the service’s latest-record view.

## Change an entry definition

Edit the entry service, HTTP method/path or operation name in the application definition. If the actual route is /assist, the entry definition must match it. An old route does not automatically match a newly configured entry point.