When refreshing a stream, do other tables also get refreshed? If so, why is that? Any way i can just refresh one stream?

No, refreshing a single stream does not refresh other streams. Airbyte supports stream-level refresh operations that are fully isolated from one another. Refreshing a single stream: You can trigger a refresh for just one stream directly from the UI: 1. Navigate to the Connection's Status page. 2. Click the three grey dots next to the stream you want to refresh. 3. Select "Refresh stream" — this will re-sync all historical data for that stream only, leaving all other streams unaffected. [Per-stream actions] Stream independence: Each stream within a connection has its own independent state. Clearing or refreshing one stream will only affect that stream's generation ID and data — other streams are completely unaffected. [Refresh FAQ] Note on older versions: In older versions of Airbyte (e.g., OSS 0.40.18), there was a known issue where a schema change on one stream could trigger a reset for all streams. This was resolved in later versions (OSS 0.40.25+), where only the affected stream is reset upon a schema change. [Forum: Reset only one stream] During a Refresh Sync, streams that are not being refreshed will continue to sync normally to minimize data latency. [Refreshing your data] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai Okay then it's just misleading that all streams would show syncing status in the ui

That's a reasonable observation! The knowledge sources do explain this behavior: When a Refresh Sync is running on one stream, the other streams in the connection also sync normally during that same job in order to lower data latency. [Refreshing your data] So what you're seeing in the UI isn't misleading per se — those other streams are actually syncing (their normal incremental sync), they're just not being refreshed. The refresh is isolated to the stream you selected, but Airbyte takes the opportunity to also run a normal sync on the remaining streams. That said, the knowledge sources don't go into detail about exactly how the UI labels or distinguishes between a stream that is being refreshed vs. one that is just syncing normally during the same job. If the UI shows the same "syncing" status for both without differentiation, that could indeed be a source of confusion. You may want to raise that as a UX feedback point with Airbyte directly. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai is there a way to not sync other jobs/tables?

The knowledge sources do not explicitly mention a built-in option to prevent other streams from syncing normally during a single-stream refresh. As noted, Airbyte intentionally syncs non-refreshed streams during a Refresh Sync to lower data latency. [Refreshing your data] However, a potential workaround mentioned in the community is to split streams into separate connections. This way, you have full control over when each connection/stream syncs independently. [Forum: Parallel Streams] The trade-off with this approach is that it can lead to a large number of connections if you have many streams, so it may not be practical in all cases. I'd recommend reaching out to Airbyte's community Slack or opening a GitHub issue if this is a critical need, as the knowledge sources don't provide a more direct solution. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.