feat(connections): add pausedSyncs to connection list API by agusayerza · Pull Request #5699 · NangoHQ/nango

agusayerza · 2026-03-24T21:24:24Z

Add pausedSyncs field to the connections list API response.

We want to show which connections have paused syncs on the FE when listing connections. For each page of connections returned, we fetch their syncs from the DB and do a targeted lookup to the orchestrator using exact schedule names, bounded by page size (~20 connections) rather than the full environment.

Add pausedSyncs: string[] to ApiConnectionSimple type
Add getSyncsByConnectionIds() to sync service
Use existing Orchestrator.searchSchedules() with exact names for the current page
Graceful fallback: orchestrator errors log and return empty pausedSyncs rather than 500ing the entire list endpoint

This change also formalizes the enrichment flow across shared contracts and service boundaries, including safer failure handling and tighter validation on schedule-search inputs, so paused-sync visibility is added in a resilient, bounded way without compromising the stability of the connections listing path.

This summary was automatically generated by @propel-code-bot

linear · 2026-03-24T21:24:28Z

NAN-5076 Connection list view refresh

marcindobry · 2026-03-24T22:50:01Z

+                provider: data.provider,
+                activeLog: data.active_logs,
+                endUser: data.end_user,
+                hasPausedSyncs: pausedConnectionIds.has(data.connection.id)


Could we instead return a list of paused sync names and let the client figure out the boolean just based on .length > 0? We've done all the heavy lifting for it already at this point and so it's more information for free.

TBonnin · 2026-03-25T13:13:50Z

+};
+
+export async function up(knex: Knex): Promise<void> {
+    await knex.raw(`CREATE INDEX CONCURRENTLY IF NOT EXISTS "idx_schedules_paused_name" ON ${SCHEDULES_TABLE} (name) WHERE state = 'PAUSED';`);


have you run an EXPLAIN on the search query? Given how small schedules table is, this index might not be even needed

I had run an explain, with the old approach it would perform better, but its hard to tell if worth it. Now that we call it by page, it makes no sense so I dropped the index. Old approach seq scanned 74K rows in ~50ms without the index, for reference. The new approach hits schedules_unique_name and finishes in 0.1ms

TBonnin · 2026-03-25T13:15:13Z

@@ -14,6 +14,8 @@ type PostSearch = Endpoint<{
    Path: typeof path;
    Body: {
        names?: string[] | undefined;
+        namePrefix?: string | undefined;


is it better to add a new explicit param or to support wildcard in the existing names one?

No longer needed

TBonnin · 2026-03-25T13:23:41Z

@@ -23,6 +25,8 @@ type PostSearch = Endpoint<{
 const bodySchema = z
    .object({
        names: z.array(z.string().min(1)).optional(),
+        namePrefix: z.string().min(1).optional(),
+        state: z.enum(['STARTED', 'PAUSED', 'DELETED']).optional(),


recently found out you can use satisfies ScheduleState[] to prevent accidentally having an enum value that doesn't exist.

TBonnin · 2026-03-25T13:29:39Z

@@ -114,6 +123,19 @@ export class Orchestrator {
        return Ok(scheduleMap);
    }

+    async getPausedSyncsByEnvironment({ environmentId }: { environmentId: number }): Promise<Result<string[]>> {
+        const namePrefix = `environment:${environmentId}:sync:`;


let's expose the prefix from the orchestrator.ts to avoid duplication and make sure we only need to change it in one place if needed

No longer needed

TBonnin · 2026-03-25T13:39:35Z

@@ -114,6 +123,19 @@ export class Orchestrator {
        return Ok(scheduleMap);
    }

+    async getPausedSyncsByEnvironment({ environmentId }: { environmentId: number }): Promise<Result<string[]>> {
+        const namePrefix = `environment:${environmentId}:sync:`;
+        const result = await this.client.searchSchedulesByPrefix({ namePrefix, state: 'PAUSED', limit: 10_000 });


this limit might quickly fall apart for Linux Foundation. That's also a huge amount of data to transfer when the only thing we are interested in is a boolean.
What about a new orchestrator endpoint like GET /stats?name_prefix=... that return a count per state for now

I changed the DB approach to only take into consideration the connections loaded on the current page, that way we have it scoped down and don't need to resolve every sync to display the icon

propel-code-bot

Review found no issues with the changes made.

Status: No Issues Found | Risk: Low

Review Details

📁 5 files reviewed | 💬 0 comments

Instruction Files

└── .claude/
    ├── agents/
    │   └── nango-docs-migrator.md
    └── skills

pfreixes · 2026-03-27T09:33:45Z

+    if (syncs.length > 0) {
+        const scheduleResult = await orchestrator.searchSchedules(syncs.map((s) => ({ syncId: s.id, environmentId: environment.id })));
+        if (scheduleResult.isErr()) {
+            res.status(500).send({ error: { code: 'server_error' } });


should we log the error or have it attached to the span somehow? otherwise will be tough to know what caused the error

TBonnin · 2026-03-27T13:43:50Z

+    const connectionIds = connections.map((data) => data.connection.id);
+    const syncs = await getSyncsByConnectionIds({ connectionIds });
+    if (syncs.length > 0) {
+        const scheduleResult = await orchestrator.searchSchedules(syncs.map((s) => ({ syncId: s.id, environmentId: environment.id })));


let's add some safeguard to orchestrator postSearch and max the length of names to a high value that is not infinite, so we don't happen to send a huge number by accident

TBonnin · 2026-03-27T13:45:28Z

+    }
+    return db.knex.select('id', 'name', 'nango_connection_id').from<Sync>(TABLE).whereIn('nango_connection_id', connectionIds).andWhere({ deleted: false });
+};
+


can we make all new functions that can fail return a Result?

Add hasPausedSyncs field to the connections list API response. Instead of fetching all syncs for the page's connections and querying orchestrator for each state, we now reverse the lookup: ask orchestrator for all PAUSED schedules in the environment first (fast path returns immediately when nothing is paused), then resolve only those sync IDs back to connection IDs. - Add partial index (name) WHERE state = 'PAUSED' on schedules table - Extend scheduler/orchestrator search to support namePrefix + state - Add Orchestrator.getPausedSyncsByEnvironment() - Add getSyncsByIds() to sync service - Add hasPausedSyncs to ApiConnectionSimple type

Refresh the connections list UI with improved filtering and status indicators https://www.figma.com/design/2MyZwo8A4D2XRIOhXL3cZ8/CURRENT-%F0%9F%90%BA-Design-Sytem---Product?node-id=9094-77970&m=dev [Loom demo](https://www.loom.com/share/0c3d7958981b43f59088471464dcb0ae) - Replace MultiSelect with new Combobox component (single + multi-select) - Add granular Status filter: OK, Error, Auth error, Sync error, Paused syncs - Status filter persisted in URL query params - Show hasPausedSyncs indicator per connection row - Integration filter now shows logos and "Add integration" footer CTA   Requires NangoHQ#5699 to be merged NAN-5076   --- This update also standardizes filtering behavior by combining URL-backed status state with frontend status composition logic layered on top of existing backend error filtering, while introducing reusable UI building blocks intended to support richer filter hierarchies and status rendering patterns across the app. --- *This summary was automatically generated by @propel-code-bot*

agusayerza requested a review from a team March 24, 2026 21:24

This comment was marked as outdated.

Sign in to view

marcindobry requested changes Mar 24, 2026

View reviewed changes

TBonnin reviewed Mar 25, 2026

View reviewed changes

agusayerza force-pushed the agus/NAN-5076/connection-list-refresh-be branch from 3b958df to 26ba24a Compare March 26, 2026 17:08

This comment was marked as outdated.

Sign in to view

agusayerza requested a review from marcindobry March 26, 2026 17:13

propel-code-bot Bot reviewed Mar 26, 2026

View reviewed changes

agusayerza changed the title ~~feat(connections): efficient paused syncs detection via reverse lookup~~ feat(connections): add pausedSyncs to connection list API Mar 26, 2026

agusayerza requested a review from a team March 26, 2026 17:30

pfreixes reviewed Mar 27, 2026

View reviewed changes

TBonnin reviewed Mar 27, 2026

View reviewed changes

agusayerza added 5 commits April 2, 2026 09:48

PR comment fixes

d6d176c

Return paused syncs names

4224d9c

Graceful fallback

433e82c

PR fixes

77df32d

agusayerza force-pushed the agus/NAN-5076/connection-list-refresh-be branch from 86880df to 77df32d Compare April 2, 2026 15:02

agusayerza mentioned this pull request Apr 2, 2026

feat(webapp): Connection list view refresh #5776

Closed

marcindobry approved these changes Apr 2, 2026

View reviewed changes

agusayerza added this pull request to the merge queue Apr 7, 2026

Merged via the queue into master with commit 16d98d4 Apr 7, 2026
25 checks passed

agusayerza deleted the agus/NAN-5076/connection-list-refresh-be branch April 7, 2026 21:18

agusayerza mentioned this pull request Apr 7, 2026

feat(webapp): connection list view refresh #5806

Merged

Conversation

agusayerza commented Mar 24, 2026 • edited by propel-code-bot Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

linear Bot commented Mar 24, 2026

Uh oh!

This comment was marked as outdated.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This comment was marked as outdated.

Uh oh!

propel-code-bot Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

agusayerza commented Mar 24, 2026 •

edited by propel-code-bot Bot

Loading