fix(asana): honour the pinned-project exception on the task rehydrate path

listDocuments deliberately keeps syncing a project the user pinned via the
`project` config field even once it is archived, but getDocument ignored
sourceConfig and applied the all-parents-archived exclusion unconditionally.
For a pinned archived project the listing kept emitting its tasks while every
hydration returned null, so new tasks were dropped as empty and already-indexed
ones were frozen at their last content.

isTaskUnderActiveProject now takes the pinned project gid and keeps any task
reachable through it, matching the listing exactly. The unpinned path is
unchanged and still fails open on missing/non-boolean archived values.

Author: waleedlatif1

apps/sim/connectors/asana/asana.test.ts

@@ -118,6 +118,30 @@ describe('isTaskUnderActiveProject', () => {
       } as unknown as typeof baseTask)
     ).toBe(true)
   })
+
+  it.concurrent('keeps a task reachable through the pinned project even once archived', () => {
+    expect(
+      isTaskUnderActiveProject(
+        {
+          ...baseTask,
+          projects: [{ gid: 'p1', name: 'Pinned', archived: true }],
+        },
+        'p1'
+      )
+    ).toBe(true)
+  })
+
+  it.concurrent('still excludes an all-archived task when the pinned project is elsewhere', () => {
+    expect(
+      isTaskUnderActiveProject(
+        {
+          ...baseTask,
+          projects: [{ gid: 'p1', name: 'Old', archived: true }],
+        },
+        'p9'
+      )
+    ).toBe(false)
+  })
 })
 
 describe('decideTaskCap', () => {

apps/sim/connectors/asana/asana.ts

@@ -113,10 +113,17 @@ export function isActiveProject(project: AsanaProject): boolean {
  * array, or any entry whose `archived` is missing or non-boolean is kept. A
  * task that still sits in at least one active project is kept, matching the
  * listing, which reaches it through that active project.
+ *
+ * `pinnedProjectGid` mirrors the listing's pinned-project exception: when the
+ * user configured a specific `project`, the listing keeps syncing it even once
+ * archived, so a task reachable through that project must survive rehydration
+ * too. Without this the listing would keep emitting the task while every
+ * hydration returned `null`, stranding it as permanently empty.
  */
-export function isTaskUnderActiveProject(task: AsanaTask): boolean {
+export function isTaskUnderActiveProject(task: AsanaTask, pinnedProjectGid?: string): boolean {
   const projects = task.projects
   if (!Array.isArray(projects) || projects.length === 0) return true
+  if (pinnedProjectGid && projects.some((project) => project?.gid === pinnedProjectGid)) return true
   return !projects.every((project) => project?.archived === true)
 }
 
@@ -382,9 +389,10 @@ export const asanaConnector: ConnectorConfig = {
 
   getDocument: async (
     accessToken: string,
-    _sourceConfig: Record<string, unknown>,
+    sourceConfig: Record<string, unknown>,
     externalId: string
   ): Promise<ExternalDocument | null> => {
+    const pinnedProjectGid = (sourceConfig.project as string) || undefined
     try {
       const result = await asanaGet<{ data: AsanaTask }>(
         accessToken,
@@ -394,7 +402,7 @@ export const asanaConnector: ConnectorConfig = {
 
       if (!task) return null
 
-      if (!isTaskUnderActiveProject(task)) {
+      if (!isTaskUnderActiveProject(task, pinnedProjectGid)) {
         logger.info('Skipping Asana task whose projects are all archived', { externalId })
         return null
       }