Conversation
…er mode on employee-access
…ss two check files
CS-168 Filter employees based on org unit and filter mode in employee-access check
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
PR SummaryMedium Risk Overview File parsing paths are expanded/changed. Questionnaire content extraction adds Trigger.dev jobs and integrations get robustness tweaks. Written by Cursor Bugbot for commit 8fd4607. This will update automatically on new commits. Configure here. |
… async processing - Changed API response to return runId and publicAccessToken instead of questionnaireId and totalQuestions for real-time tracking. - Enhanced file handling to support async parsing of questionnaires, including improved error handling for file uploads. - Updated content extraction to handle PDF and DOCX formats using Claude's capabilities. - Added tests for new PDF extraction logic and updated existing tests to cover new functionality.
- Updated maxDuration for parseQuestionnaireTask and processKnowledgeBaseDocumentsOrchestratorTask to reflect correct time in seconds instead of milliseconds.
- Enhanced the questionnaire service to include fileSize in the upload data. - Updated parseQuestionnaireTask to handle fileSize, allowing for more accurate file handling during parsing.
…tionnaire [dev] [tofikwest] tofik/fix-knowledge-base-questionnaire
apps/app/src/app/(app)/[orgId]/questionnaire/hooks/useQuestionnaireParse.ts
Show resolved
Hide resolved
…acking - Changed comment to clarify the transition from upload completion to async parsing tracking in useQuestionnaireParse hook.
[dev] [tofikwest] tofik/upload-file-update-status
- Changed model name from 'claude-3-5-sonnet' to 'claude-sonnet-4-6' in the logging output of the parseQuestionsWithClaude function to reflect the current model in use.
[dev] [tofikwest] tofik/fix-log-model-name
|
🎉 This PR is included in version 3.11.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| questionsAndAnswers: questionsAndAnswers.map((qa) => ({ | ||
| question: qa.question, | ||
| answer: null, | ||
| sources: undefined, |
There was a problem hiding this comment.
Source field lost in async task flow
Low Severity
The source field from UploadAndParseDto (which can be 'internal' or 'external') is no longer propagated to the parse-questionnaire task payload. The old synchronous flow explicitly passed source: dto.source || 'internal' to persistQuestionnaireResult, but the new async flow omits it entirely from the tasks.trigger call. The task's db.questionnaire.create also doesn't set source, relying on the Prisma @default("internal"). This silently drops the source value for any caller passing 'external'.


This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.