Is there a way to "Refresh your data" only one of ...
# ask-ai
y
Is there a way to "Refresh your data" only one of the tables configured in the sync?
k
Yes. Airbyte supports refreshing data at the stream (table) level, not only at the whole-connection level. From the Refresh/Refreshing your data docs, refreshes “can be triggered from the UI and via the Airbyte API at either the stream or connection levels” for supported destinations and depending on your sync mode.[[Refreshes 1.6](https://docs.airbyte.com/platform/1.6/operator-guides/refreshes); [Refreshes next](https://docs.airbyte.com/platform/next/operator-guides/refreshes)] So if your connection and destination support refreshes, you can: - Trigger a Refresh Sync for a single stream (table) instead of all streams. - Choose the appropriate refresh type (e.g., Refresh stream and remove records vs retain records) depending on your sync mode.[[Refreshes 1.8](https://docs.airbyte.com/platform/1.8/operator-guides/refreshes)] If you instead want to fully delete and reload just one table, you can use Clear data on a single stream, which also operates at stream level.[[Clearing data](https://docs.airbyte.com/platform/operator-guides/clear)]
y
@kapa.ai What does refreshing stream do? Dropping and recreate the table?
k
A message from kapa.ai
A Refresh Sync does not literally say it “drops and recreates” the destination table in the docs. What it does, conceptually: - It erases the current cursor for any incremental streams, “rewinding” them so Airbyte reads from the beginning again.[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] - While the refresh runs, **existing destination data stays queryable**; only at successful completion is the newly refreshed data swapped or merged into place.[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] - Depending on sync mode and refresh option: - Refresh stream and remove records → final tables show only data newly synced since the refresh began.[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] - Refresh stream and retain records → merge new data with previously stored data, keeping history.[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] The exact low‑level mechanism (e.g., whether a destination “drops and recreates” a table or uses temp tables and swaps/merges) is destination-specific and not fully detailed for refreshes in the docs. The full‑refresh pages explain that some destinations recreate tables using a
final-table-tmp
pattern, but they also note this “will vary wildly from destination to destination.”[[Full refresh overwrite](https://docs.airbyte.com/platform/using-airbyte/core-concepts/sync-modes/full-refresh-overwrite)] So: conceptually, refresh re‑pulls data and then swaps/merges it into the final tables; whether that is implemented as a physical drop/recreate is destination‑dependent and not explicitly specified.
y
@kapa.ai When you refresh a stream for a table, do the other tables in the same connection get refreshed too? I just triggered one table's stream refresh and see other tables being synced
k
A message from kapa.ai
Refreshing a single stream does not refresh the other streams’ data or reset their cursors/state. Only the selected stream is “rewound.”[[Refresh FAQ 1.8](https://docs.airbyte.com/platform/1.8/operator-guides/refreshes#frequently-asked-questions-faq)] However, during a Refresh Sync: - Airbyte explicitly states that **“the streams that are not being refreshed will also sync normally in order to lower data latency.”**[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] So what you’re seeing is expected: - The target stream is being refreshed (cursor reset, data re‑read). - The other streams in the same connection are just running a normal sync, not a refresh. Their state and generation IDs are unchanged.[[Refresh FAQ 1.8](https://docs.airbyte.com/platform/1.8/operator-guides/refreshes#frequently-asked-questions-faq)]
y
@kapa.ai Can you schedule a stream refresh? via the api or the ui?
k
A message from kapa.ai
Based on the docs, a Refresh Sync can be triggered from the UI or via the API, and it can be applied at the stream or connection level.[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] However, the documentation only describes on‑demand triggering (clicking refresh / calling the API) and does not mention any way to schedule a refresh (e.g., “run a refresh every week”) either in the UI or via a built‑in scheduling field.[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] The scheduling docs cover only regular sync schedules: fixed intervals, CRON, or manual, and do not mention scheduling refresh operations.[[Sync schedules](https://docs.airbyte.com/platform/using-airbyte/core-concepts/sync-schedules)] So, from the available documentation: - You can trigger a refresh via UI or API. - There is no documented feature to schedule refreshes themselves; you would need to orchestrate that externally (e.g., your own scheduler calling the refresh API), but this is not described in the official docs.
y
@kapa.ai where is the doc on the refresh stream api?
k
A message from kapa.ai
The docs you’ve shared only say that refreshes can be triggered via the Airbyte API, but they do not include or link to a specific “Refresh Stream API” endpoint description. They point generically to the full API reference at: - [reference.airbyte.com](https://reference.airbyte.com/reference/getting-started)[[Platform API 1.8](https://docs.airbyte.com/platform/1.8/api-documentation); [Developers API docs](https://docs.airbyte.com/developers/api-documentation)] and mention that both types of Refresh Syncs “can be triggered from the UI and via the Airbyte API at either the stream or connection levels.”[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] However, in the provided knowledge sources there is no direct example or path like “POST /v1/…/refresh_stream” documented, nor a dedicated page that shows the exact request body for a refresh stream call. So, based on what we have: - The existence of a refresh operation via API is documented conceptually.[[Refreshing data](https://docs.airbyte.com/platform/operator-guides/refreshes)] - The concrete endpoint and payload for “refresh stream” are not detailed in these sources; you’d need to look them up directly in the live API reference at
<http://reference.airbyte.com|reference.airbyte.com>
.