# Edit, pause and delete connections > Run a sync now, change what a connection syncs and when, stop it running, and delete it. Includes what the console can and cannot change after setup. Everything you do to an existing connection starts on its own page. Select a connection in **Data · Connections** to open it. The header shows the connection's name and status, and beneath it the source, the warehouse it lands in and its frequency. Two buttons sit on the right: **Check status** and **Sync now**. They appear once the connection has been handed to sanda's managed sync, which happens when you save its streams. Three tabs organise the rest: | Tab | What is on it | |---|---| | **Status** | Any error, the run panel, the four figures, the **Streams** panel and where rows land | | **Timeline** | The last ten runs. See [Monitor syncs](https://docs.sanda-os.com.au/connections/monitor-syncs) | | **Settings** | **Details**, **Schedule**, **Network** and the delete control | Owners and admins can do everything on this page. Members can open it and read it, but the controls refuse them with **Only owners and admins can manage connections.** ## Run a sync now Press **Sync now** to run a connection without waiting for its schedule. The **Status** tab opens on the run panel at once, before sanda has heard back, so you see the run start. While a run is in progress the button reads **Syncing** and is disabled. **Sync now** is refused, with the reason on the page, when the workspace is suspended. A workspace whose warehouse was suspended for its monthly budget, or whose free trial has ended or used up its credit, cannot sync. The message says when it happened and where to lift it. See [Usage and suspension](https://docs.sanda-os.com.au/warehouse/usage-and-suspension). cherry can start a sync for you as well. Depending on your cherry settings, it asks you to confirm first. See [Actions and approvals](https://docs.sanda-os.com.au/cherry/actions-and-approvals). ## Check status **Check status** re-reads the latest run and updates the page. You rarely need it while a run is going, because the page follows the run itself. It is for the times when the page may be behind, such as after a scheduled run you were not watching, or after you fixed something that was stopping tables from becoming readable. See [Monitor syncs](https://docs.sanda-os.com.au/connections/monitor-syncs#keeping-the-page-up-to-date). ## Change what syncs On the **Status** tab, press **Edit streams** in the **Streams** panel. Tick tables on or off, change a mode, and set a cursor or primary key. The change applies from the next sync. See [Choose what to sync](https://docs.sanda-os.com.au/connections/choose-streams). Turning a stream off stops it being synced. The table it landed earlier stays in your warehouse and is no longer refreshed. ## Change the schedule On the **Settings** tab, the **Schedule** panel has the same picker as setup. Choose a frequency and press **Save schedule**. The change applies from the next run. See [Sync schedules](https://docs.sanda-os.com.au/connections/schedules). ## Pause a connection There is no **Pause** button. To stop a connection running on its own, open **Settings**, choose **Manual** in the **Schedule** panel and press **Save schedule**. The connection keeps its streams, its settings and every row it has landed, and it runs only when you press **Sync now**. To start scheduled runs again, save a schedule. A connection can also read **Paused** in the list. If you did not expect that, contact sanda support. ## What you cannot change after setup The console shows a connection's **Details** on the **Settings** tab as read-only: its **Name**, **Source**, **Destination**, **Frequency**, **Landing prefix** and **Created** date. There is no control to rename a connection, move it to another warehouse, or change its source. The name also decides the landing prefix: every table the connection lands is named from it. ### Sign-in details While a connection has not connected yet, for example because you skipped the details or connecting failed, the **Status** tab offers **Finish setting up this connection** with **Enter connection details**. That form is the same as the one in setup. Once a connection has connected, the console has no field for changing its sign-in details. If a password is rotated or a key is revoked, and the connection starts failing, contact sanda support rather than deleting and recreating it. A new connection with the same name lands in the same tables as the old one. ### Starting a table again There is no reset button. A full refresh mode reads a whole table on every run, so it needs no reset. If you need an incremental table read again from the start, contact sanda support. ## Delete a connection Deleting stops the connection and removes it from sanda. Rows that already landed stay in your warehouse. :::steps 1. **Open Settings.** On the connection's page, go to the **Settings** tab. 2. **Press Delete connection.** It is in the **Danger zone** at the bottom, under the sentence **Deleting … stops its schedule and removes it from sanda. Rows already landed stay in your warehouse.** 3. **Confirm.** The button changes. Press **Yes, delete it**, or **Keep it** to back out. It is two presses on the same page, with no dialog. ::: :::danger Deleting cannot be undone. The connection's run history goes with it, and you would have to add the connection again and choose its streams again. ::: ### What happens to your data | | After you delete | |---|---| | **The landed tables** | They stay in your warehouse, as they were after the last successful run. Nothing refreshes them any more | | **Storage** | They keep counting toward your warehouse's storage. To have them removed, contact sanda support | | **Your semantic map and reports** | Untouched. Anything built on those tables keeps reading them, and shows the data as of the last sync | | **Tasks and indexes set to run after this connection syncs** | They lose that trigger and no longer run when it would have synced. Give them another schedule | | **The run history** | Deleted with the connection | | **The schedule** | Stopped | sanda also removes the connection and its stored source from its managed sync. If that cleanup cannot be completed at that moment, the deletion still goes through in sanda. The deletion is recorded in **Overview · Recent activity** as **Connection removed**. :::links - [Monitor syncs](https://docs.sanda-os.com.au/connections/monitor-syncs): Runs, history and what each status means. - [Choose what to sync](https://docs.sanda-os.com.au/connections/choose-streams): Streams, modes, cursors and keys. - [Troubleshoot connections](https://docs.sanda-os.com.au/connections/troubleshooting): When a run fails. :::