Skip to content

Comments

Fix bulk process error#891

Merged
elie222 merged 1 commit intomainfrom
fix/bulk-process
Nov 2, 2025
Merged

Fix bulk process error#891
elie222 merged 1 commit intomainfrom
fix/bulk-process

Conversation

@elie222
Copy link
Owner

@elie222 elie222 commented Nov 2, 2025

Note

Improves bulk email processing by adding input validation, robust fetch error handling with toasts, and safer pagination parameters.

  • Assistant bulk processing (apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx):
    • Add validation for startDate and emailAccountId; update button disabled state and show error toasts when missing.
    • Enhance fetch handling: surface non-OK responses via toasts, guard against missing threads, and log errors.
    • Adjust ThreadsQuery: set before to endDate; pass nextPageToken only when present.
  • Version:
    • Bump version.txt to v2.17.23.

Written by Cursor Bugbot for commit b9840b4. Configure here.

Summary by CodeRabbit

  • Bug Fixes
    • Added validation and error messages for missing prerequisites when starting bulk rules.
    • Enhanced error handling for API requests with detailed feedback during batch processing.
    • Improved response validation to ensure data integrity during operations.

@vercel
Copy link

vercel bot commented Nov 2, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
inbox-zero Ready Ready Preview Nov 2, 2025 1:57pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 2, 2025

Walkthrough

Enhanced error handling and validation in bulk email processing component. Added user-facing error messages with toast notifications for missing prerequisites (start date, email account ID). Improved API fetch loop with nextPageToken support, consistent error handling for failed responses, and response structure validation to prevent invalid data processing.

Changes

Cohort / File(s) Summary
Version Management
version.txt
Version bump from v2.17.22 to v2.17.23
Bulk Run Component
apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
Added validation and error handling for missing start date and email account ID; enhanced API fetch loop with nextPageToken inclusion, improved error responses, and response structure validation; updated button disabled state logic with early returns and toast notifications for user feedback

Sequence Diagram

sequenceDiagram
    actor User
    participant UI as BulkRunRules Component
    participant API as Gmail API
    participant Toast as Error Notification

    User->>UI: Click Start Bulk Run
    
    rect rgba(255, 200, 100, 0.3)
    Note over UI: Validation Phase
    UI->>UI: Check startDate exists
    UI->>UI: Check emailAccountId exists
    alt Missing Prerequisites
        UI->>Toast: Show validation error toast
        UI->>User: Disable Start button
    end
    end
    
    rect rgba(100, 200, 150, 0.3)
    Note over UI,API: API Fetch Loop
    loop Fetch batches with pagination
        UI->>API: Fetch threads (with nextPageToken)
        alt Request fails
            API-->>UI: Error response
            UI->>Toast: Show fetch error toast
            UI->>UI: Break loop
        else Request succeeds
            API-->>UI: Response with threads
            alt Invalid response structure
                UI->>UI: Check data.threads exists
                alt Invalid structure
                    UI->>Toast: Show validation error toast
                    UI->>UI: Abort processing
                end
            else Valid structure
                UI->>UI: Process threads batch
                UI->>UI: Update nextPageToken
            end
        end
    end
    end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Single file with cohesive error handling enhancements
  • Changes follow consistent patterns (validation checks, error toasts, early returns)
  • All modifications are additive error-handling logic without architectural changes

Areas to review:

  • Correctness of validation conditions (startDate and emailAccountId checks)
  • Proper error toast messaging and user clarity
  • API loop termination logic on errors (early break behavior)
  • Response structure validation for data.threads presence

Poem

🐰 With error messages now crystal clear,
And toast notifications drawing near,
The bulk run's journey's smooth and sound,
Validation checks are safe and found! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The PR title "Fix bulk process error" is related to the main changes in the changeset, which comprise enhancements to the BulkRunRules component including added validation, error messaging with toasts, and improved error handling during batch processing. The title refers to a real and significant aspect of the changes (the bulk process fixes), though it is somewhat generic and doesn't fully capture the comprehensive scope of improvements made, such as the API enhancements and validation additions. However, it remains sufficiently clear that the primary focus is on fixing issues within the bulk run process.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/bulk-process

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd2af9a and b9840b4.

📒 Files selected for processing (2)
  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx (3 hunks)
  • version.txt (1 hunks)
🧰 Additional context used
📓 Path-based instructions (14)
apps/web/**/*.{ts,tsx}

📄 CodeRabbit inference engine (apps/web/CLAUDE.md)

apps/web/**/*.{ts,tsx}: Use TypeScript with strict null checks
Path aliases: Use @/ for imports from project root
Use proper error handling with try/catch blocks
Format code with Prettier
Leverage TypeScript inference for better DX

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
apps/web/app/**

📄 CodeRabbit inference engine (apps/web/CLAUDE.md)

NextJS app router structure with (app) directory

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
apps/web/**/*.tsx

📄 CodeRabbit inference engine (apps/web/CLAUDE.md)

apps/web/**/*.tsx: Follow tailwindcss patterns with prettier-plugin-tailwindcss
Prefer functional components with hooks
Use shadcn/ui components when available
Ensure responsive design with mobile-first approach
Follow consistent naming conventions (PascalCase for components)
Use LoadingContent component for async data
Use result?.serverError with toastError and toastSuccess
Use LoadingContent component to handle loading and error states consistently
Pass loading, error, and children props to LoadingContent

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
!{.cursor/rules/*.mdc}

📄 CodeRabbit inference engine (.cursor/rules/cursor-rules.mdc)

Never place rule files in the project root, in subdirectories outside .cursor/rules, or in any other location

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
  • version.txt
**/*.tsx

📄 CodeRabbit inference engine (.cursor/rules/form-handling.mdc)

**/*.tsx: Use React Hook Form with Zod for validation
Validate form inputs before submission
Show validation errors inline next to form fields

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/logging.mdc)

**/*.{ts,tsx}: Use createScopedLogger for logging in backend TypeScript files
Typically add the logger initialization at the top of the file when using createScopedLogger
Only use .with() on a logger instance within a specific function, not for a global logger

Import Prisma in the project using import prisma from "@/utils/prisma";

**/*.{ts,tsx}: Don't use TypeScript enums.
Don't use TypeScript const enum.
Don't use the TypeScript directive @ts-ignore.
Don't use primitive type aliases or misleading types.
Don't use empty type parameters in type aliases and interfaces.
Don't use any or unknown as type constraints.
Don't use implicit any type on variable declarations.
Don't let variables evolve into any type through reassignments.
Don't use non-null assertions with the ! postfix operator.
Don't misuse the non-null assertion operator (!) in TypeScript files.
Don't use user-defined types.
Use as const instead of literal types and type annotations.
Use export type for types.
Use import type for types.
Don't declare empty interfaces.
Don't merge interfaces and classes unsafely.
Don't use overload signatures that aren't next to each other.
Use the namespace keyword instead of the module keyword to declare TypeScript namespaces.
Don't use TypeScript namespaces.
Don't export imported variables.
Don't add type annotations to variables, parameters, and class properties that are initialized with literal expressions.
Don't use parameter properties in class constructors.
Use either T[] or Array consistently.
Initialize each enum member value explicitly.
Make sure all enum members are literal values.

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
apps/web/app/(app)/*/**

📄 CodeRabbit inference engine (.cursor/rules/page-structure.mdc)

Components for the page are either put in page.tsx, or in the apps/web/app/(app)/PAGE_NAME folder

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
apps/web/app/(app)/*/**/*.tsx

📄 CodeRabbit inference engine (.cursor/rules/page-structure.mdc)

If you need to use onClick in a component, that component is a client component and file must start with 'use client'

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
apps/web/app/(app)/*/**/**/*.tsx

📄 CodeRabbit inference engine (.cursor/rules/page-structure.mdc)

If we're in a deeply nested component we will use swr to fetch via API

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
apps/web/app/**/*.tsx

📄 CodeRabbit inference engine (.cursor/rules/project-structure.mdc)

Components with onClick must be client components with use client directive

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

**/*.{js,jsx,ts,tsx}: Don't use elements in Next.js projects.
Don't use elements in Next.js projects.
Don't use namespace imports.
Don't access namespace imports dynamically.
Don't use global eval().
Don't use console.
Don't use debugger.
Don't use var.
Don't use with statements in non-strict contexts.
Don't use the arguments object.
Don't use consecutive spaces in regular expression literals.
Don't use the comma operator.
Don't use unnecessary boolean casts.
Don't use unnecessary callbacks with flatMap.
Use for...of statements instead of Array.forEach.
Don't create classes that only have static members (like a static namespace).
Don't use this and super in static contexts.
Don't use unnecessary catch clauses.
Don't use unnecessary constructors.
Don't use unnecessary continue statements.
Don't export empty modules that don't change anything.
Don't use unnecessary escape sequences in regular expression literals.
Don't use unnecessary labels.
Don't use unnecessary nested block statements.
Don't rename imports, exports, and destructured assignments to the same name.
Don't use unnecessary string or template literal concatenation.
Don't use String.raw in template literals when there are no escape sequences.
Don't use useless case statements in switch statements.
Don't use ternary operators when simpler alternatives exist.
Don't use useless this aliasing.
Don't initialize variables to undefined.
Don't use the void operators (they're not familiar).
Use arrow functions instead of function expressions.
Use Date.now() to get milliseconds since the Unix Epoch.
Use .flatMap() instead of map().flat() when possible.
Use literal property access instead of computed property access.
Don't use parseInt() or Number.parseInt() when binary, octal, or hexadecimal literals work.
Use concise optional chaining instead of chained logical expressions.
Use regular expression literals instead of the RegExp constructor when possible.
Don't use number literal object member names th...

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
!pages/_document.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

!pages/_document.{js,jsx,ts,tsx}: Don't import next/document outside of pages/_document.jsx in Next.js projects.
Don't import next/document outside of pages/_document.jsx in Next.js projects.

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
  • version.txt
**/*.{jsx,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

**/*.{jsx,tsx}: Don't destructure props inside JSX components in Solid projects.
Don't use both children and dangerouslySetInnerHTML props on the same element.
Don't use Array index in keys.
Don't assign to React component props.
Don't define React components inside other components.
Don't use event handlers on non-interactive elements.
Don't assign JSX properties multiple times.
Don't add extra closing tags for components without children.
Use <>...</> instead of ....
Don't insert comments as text nodes.
Don't use the return value of React.render.
Make sure all dependencies are correctly specified in React hooks.
Make sure all React hooks are called from the top level of component functions.
Don't use unnecessary fragments.
Don't pass children as props.
Use semantic elements instead of role attributes in JSX.

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
**/*.{html,jsx,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

**/*.{html,jsx,tsx}: Don't use or elements.
Don't use accessKey attribute on any HTML element.
Don't set aria-hidden="true" on focusable elements.
Don't add ARIA roles, states, and properties to elements that don't support them.
Only use the scope prop on elements.
Don't assign non-interactive ARIA roles to interactive HTML elements.
Make sure label elements have text content and are associated with an input.
Don't assign interactive ARIA roles to non-interactive HTML elements.
Don't assign tabIndex to non-interactive HTML elements.
Don't use positive integers for tabIndex property.
Don't include "image", "picture", or "photo" in img alt prop.
Don't use explicit role property that's the same as the implicit/default role.
Make static elements with click handlers use a valid role attribute.
Always include a title element for SVG elements.
Give all elements requiring alt text meaningful information for screen readers.
Make sure anchors have content that's accessible to screen readers.
Assign tabIndex to non-interactive HTML elements with aria-activedescendant.
Include all required ARIA attributes for elements with ARIA roles.
Make sure ARIA properties are valid for the element's supported roles.
Always include a type attribute for button elements.
Make elements with interactive roles and handlers focusable.
Give heading elements content that's accessible to screen readers (not hidden with aria-hidden).
Always include a lang attribute on the html element.
Always include a title attribute for iframe elements.
Accompany onClick with at least one of: onKeyUp, onKeyDown, or onKeyPress.
Accompany onMouseOver/onMouseOut with onFocus/onBlur.
Include caption tracks for audio and video elements.
Make sure all anchors are valid and navigable.
Ensure all ARIA properties (aria-*) are valid.
Use valid, non-abstract ARIA roles for elements with ARIA roles.
Use valid ARIA state and property values.
Use valid values for the autocomplete attribute on input eleme...

Files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
🧠 Learnings (7)
📚 Learning: 2025-07-18T15:04:44.818Z
Learnt from: CR
Repo: elie222/inbox-zero PR: 0
File: .cursor/rules/data-fetching.mdc:0-0
Timestamp: 2025-07-18T15:04:44.818Z
Learning: Applies to {app,components}/**/*.{ts,tsx} : Use `result?.serverError` with `toastError` and `toastSuccess` for error handling; success toast is optional

Applied to files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
📚 Learning: 2025-07-18T15:05:16.146Z
Learnt from: CR
Repo: elie222/inbox-zero PR: 0
File: .cursor/rules/fullstack-workflow.mdc:0-0
Timestamp: 2025-07-18T15:05:16.146Z
Learning: Applies to apps/web/components/**/*.tsx : Use the `LoadingContent` component to handle loading and error states consistently in data-fetching components.

Applied to files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
📚 Learning: 2025-07-18T15:04:30.467Z
Learnt from: CR
Repo: elie222/inbox-zero PR: 0
File: apps/web/CLAUDE.md:0-0
Timestamp: 2025-07-18T15:04:30.467Z
Learning: Applies to apps/web/**/*.tsx : Use `LoadingContent` component to handle loading and error states consistently

Applied to files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
📚 Learning: 2025-07-19T17:50:22.078Z
Learnt from: CR
Repo: elie222/inbox-zero PR: 0
File: .cursor/rules/ui-components.mdc:0-0
Timestamp: 2025-07-19T17:50:22.078Z
Learning: Applies to components/**/*.tsx : Use the `LoadingContent` component to handle loading states

Applied to files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
📚 Learning: 2025-07-18T15:04:30.467Z
Learnt from: CR
Repo: elie222/inbox-zero PR: 0
File: apps/web/CLAUDE.md:0-0
Timestamp: 2025-07-18T15:04:30.467Z
Learning: Applies to apps/web/**/*.tsx : Use `result?.serverError` with `toastError` and `toastSuccess`

Applied to files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
📚 Learning: 2025-07-18T15:04:30.467Z
Learnt from: CR
Repo: elie222/inbox-zero PR: 0
File: apps/web/CLAUDE.md:0-0
Timestamp: 2025-07-18T15:04:30.467Z
Learning: Applies to apps/web/**/*.tsx : Use LoadingContent component for async data

Applied to files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
📚 Learning: 2025-07-18T15:05:16.146Z
Learnt from: CR
Repo: elie222/inbox-zero PR: 0
File: .cursor/rules/fullstack-workflow.mdc:0-0
Timestamp: 2025-07-18T15:05:16.146Z
Learning: Applies to apps/web/components/**/*Form.tsx : Use `result?.serverError` with `toastError` and `toastSuccess` for error and success notifications in form submission handlers.

Applied to files:

  • apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx
🧬 Code graph analysis (1)
apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx (2)
apps/web/utils/fetch.ts (1)
  • fetchWithAccount (7-25)
apps/web/app/api/threads/route.ts (1)
  • ThreadsResponse (59-59)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: cubic · AI code reviewer
  • GitHub Check: Cursor Bugbot
  • GitHub Check: test
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (3)
apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx (3)

13-13: LGTM! Appropriate import for error handling.

The toastError import is correctly added to support the enhanced error notifications throughout this component.


97-112: Excellent defensive validation!

The disabled button state and early-return validation checks for both startDate and emailAccountId prevent invalid processing attempts with clear user feedback. This significantly improves the user experience.


182-185: Good pagination fix with nextPageToken.

The addition of nextPageToken to the query ensures proper pagination through batches. The before: endDate change will now pass undefined explicitly when no end date is set, which should work correctly with the API.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 2 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx">

<violation number="1" location="apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx:182">
Setting `before` to the raw `endDate` causes `before=undefined` to be sent when no end date is chosen, which fails validation and breaks bulk processing. Restore the guard so `before` is omitted when `endDate` is undefined.</violation>
</file>

React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.

limit: LIMIT,
after: startDate,
before: endDate || undefined,
before: endDate,
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Nov 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Setting before to the raw endDate causes before=undefined to be sent when no end date is chosen, which fails validation and breaks bulk processing. Restore the guard so before is omitted when endDate is undefined.

Prompt for AI agents
Address the following comment on apps/web/app/(app)/[emailAccountId]/assistant/BulkRunRules.tsx at line 182:

<comment>Setting `before` to the raw `endDate` causes `before=undefined` to be sent when no end date is chosen, which fails validation and breaks bulk processing. Restore the guard so `before` is omitted when `endDate` is undefined.</comment>

<file context>
@@ -164,21 +177,42 @@ async function onRun(
         limit: LIMIT,
         after: startDate,
-        before: endDate || undefined,
+        before: endDate,
         isUnread: true,
+        nextPageToken: nextPageToken || undefined,
</file context>
Fix with Cubic

@elie222 elie222 merged commit e1d4f9c into main Nov 2, 2025
23 checks passed
@elie222 elie222 deleted the fix/bulk-process branch November 2, 2025 14:20
@coderabbitai coderabbitai bot mentioned this pull request Dec 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant