fix(wait): address bot review — setNextResumeAt + suspend unit default

- setNextResumeAt now matches paused OR partially_resumed; otherwise the
  cron poller can't null nextResumeAt after dispatching a chained-wait
  row, so it keeps reappearing in every poll batch until execution ends
  (flagged by both greptile and bugbot)
- Suspend mode now defaults missing timeUnitLong to 'minutes' instead of
  falling back to 'seconds' and immediately erroring (flagged by bugbot)

Author: TheodoreSpeaks

apps/sim/executor/handlers/wait/wait-handler.test.ts

@@ -136,6 +136,19 @@ describe('WaitBlockHandler', () => {
     ).rejects.toThrow('Wait time exceeds maximum of 5 minutes')
   })
 
+  it('should default the suspend unit to minutes when timeUnitLong is missing', async () => {
+    vi.setSystemTime(new Date('2026-04-28T00:00:00.000Z'))
+
+    const result = (await handler.execute(mockContext, mockBlock, {
+      suspend: true,
+      timeValue: '3',
+    })) as Record<string, any>
+
+    const waitMs = 3 * 60 * 1000
+    expect(result.waitDuration).toBe(waitMs)
+    expect(result.status).toBe('waiting')
+  })
+
   it('should reject seconds as a unit when Suspend Workflow is enabled', async () => {
     await expect(
       handler.execute(mockContext, mockBlock, {

apps/sim/executor/handlers/wait/wait-handler.ts

@@ -126,7 +126,7 @@ export class WaitBlockHandler implements BlockHandler {
   ): Promise<BlockOutput> {
     const suspend = inputs.suspend === true || inputs.suspend === 'true'
     const timeValue = Number.parseFloat(inputs.timeValue || '10')
-    const timeUnit = (suspend ? inputs.timeUnitLong : inputs.timeUnit) || 'seconds'
+    const timeUnit = suspend ? inputs.timeUnitLong || 'minutes' : inputs.timeUnit || 'seconds'
 
     if (!Number.isFinite(timeValue) || timeValue <= 0) {
       throw new Error('Wait amount must be a positive number')

apps/sim/lib/workflows/executor/human-in-the-loop-manager.ts

@@ -1692,9 +1692,11 @@ export class PauseResumeManager {
   }
 
   /**
-   * Updates `next_resume_at` only when the row is still `status='paused'`.
+   * Updates `next_resume_at` only when the row is still in a poll-eligible state.
    * Guard prevents the cron poller from clobbering a freshly-written value when a
-   * concurrent manual resume has already advanced the row's state.
+   * concurrent manual resume has already advanced the row's state. `partially_resumed`
+   * rows must also be writable so the cron poller can null out their `nextResumeAt`
+   * after dispatch; otherwise the row keeps reappearing in every poll batch.
    */
   static async setNextResumeAt(args: {
     pausedExecutionId: string
@@ -1704,7 +1706,10 @@ export class PauseResumeManager {
       .update(pausedExecutions)
       .set({ nextResumeAt: args.nextResumeAt })
       .where(
-        and(eq(pausedExecutions.id, args.pausedExecutionId), eq(pausedExecutions.status, 'paused'))
+        and(
+          eq(pausedExecutions.id, args.pausedExecutionId),
+          inArray(pausedExecutions.status, ['paused', 'partially_resumed'])
+        )
       )
   }