Issues & classifications

Frontend generates a non-existent targetLigacaoId filter for custom objects while the backend enforces strict schema validation.

Background IMAP email ingestion pipeline silently fails to trigger contact auto-creation for a specific provider with no visible errors.

Request to expose GraphQL mutations and inputs for creating sidebar Folder and Link favorites that are currently missing from the API schema.

New user-facing capability to paste images into AI chat requiring frontend clipboard handling and backend vision-model integration.

Metadata API accepts and persists STANDALONE_RICH_TEXT widgets that the frontend record page does not yet render.

Navigating away from a saved view and back resets the URL and state to the default unfiltered index view.

The i18n message catalogs are not being compiled before runtime in the Docker image, so both frontend and server fall back to raw catalogs and emit warnings; fixing this likely requires build-script or container changes plus runtime load-path verification.

LLM-generated filters use object-level ilike and composite-field operators that the strict filter-arg processor rejects.

Security dependency bump to fix known axios proxy bypass CVEs; typically limited to package manifests and lockfile updates.

Dashboards are missing a filter operand that exists in views; requires aligning dashboard filter configuration with view filter logic.

Fresh Docker install failure suggests misconfiguration across compose files, install scripts, and server startup orchestration.

New BETWEEN filter operator requires coordinated changes across shared types, frontend filter UI, and backend query generation.

High-level 'email sequencer' request with no requirements, acceptance criteria, or technical scope defined.

Removing the 10-file limit and improving file-field UX requires validation, settings, and record-field component changes.

Mobile blank screen after updates indicates stale cache/token invalidation spanning frontend bootstrap, auth, and PWA layers.

CardDAV phone formatting regression for workflow contacts requires reconciling storage format differences in export logic.

Issue provides only a screenshot with no description, reproduction steps, or expected behavior for the relation search oddity.

Command menu incorrectly surfaces the manual trigger label instead of the parent workflow name for unpinned workflows.

Manifest-driven view-field contribution to existing views is an architectural change affecting manifest sync, view lifecycle, and install/uninstall cleanup.

OpenAI Zero Data Retention prevents item persistence, causing the AI chat flow to fail when it references previously stored OpenAI item IDs.

Workspace cache services query columns or properties that do not exist yet because cache recomputation runs before schema migrations during upgrades.

BlockNote-based rich text field lacks proper mobile viewport handling when the soft keyboard is open, making fullscreen and scroll interactions unreachable.

SDK-generated sync payloads include defaultValue for immutable system ACTOR fields, which the server rejects during app install or sync.

The fix for missing relationTargetFieldMetadataId only executes during the 2.3 cursor transition, so workspaces already past that point remain broken.

UI-created view fields are assigned to a different app than their parent view and field, causing a builder migration ownership mismatch during sync.

Dashboard widgets referencing a deleted app or object lack null-safety guards, causing the entire dashboard to crash.

Startup instance command check incorrectly requires all workspaces to complete a 2.3 command even on fresh installs with no prior migration state.

Microsoft email sync logic evaluates selected folders under the Sent parent without scoping to the specific subfolder, syncing the entire Sent folder instead.

Workflow update logic unexpectedly overwrites the composite emails field despite it not being included in the step's update payload.

A v1.20 upgrade migration incorrectly rewrites task/note bodyV2 fieldMetadata type from RICH_TEXT_V2 to TEXT, breaking downstream queries.

The mapUIMessagePartsToDBParts utility lacks a handler for dynamic-tool message parts, causing the AI stream to crash.

The SettingsToolsTable GraphQL query requests icon and universalIdentifier fields that were removed from the MarketplaceApp DTO.

Workspace-wide metadata SSE events push user-scoped navigation menu items into every connected client store without filtering by userWorkspaceId.

Uploaded organization logo images are persisted without stripping EXIF metadata, leaking sensitive location information.

The marketplace catalog sync service only upserts package rows and never deletes orphaned registrations that no longer exist in npm.

The MCP find_connected_accounts tool returns zero records, preventing discovery of the connectedAccountId required by draft_email.

Body contains only a link to a private issue with no public description or reproduction steps.

Sparse Sentry report indicates an anomalous consecutive external HTTP request pattern with insufficient context to narrow scope.

Front-end record creation crashes due to hardcoded many-to-many field assumptions for Tasks and Notes.

Isolated frontend UI regression where the memo field click handler or edit guard is missing in the People section.

The relation cell likely has a hard-coded or miscomputed item limit that ignores available width; a localized UI fix in the record-field/record-table components should resolve it.

Custom object type translations do not propagate to the details panel, suggesting the panel and its sub-components are using raw metadata keys instead of the localized singular/plural labels from the object metadata.

OAuth MCP integration failure spans backend authorization-server metadata, callback handling, and potentially frontend redirect logic.

Cross-cutting enhancement involving shared schema, SDK asset upload, server DB migration, GraphQL DTO, frontend rendering, and provider migration.

Registration-scoped manifest URLs are incompatible with install-scoped public assets, requiring architectural changes to asset resolution across sync, dev, and tarball deploy paths.

Enhances SDK CLI auth failure handling with TTY detection and interactive re-auth flow across deploy and dev operations.

Frontend import validation screen blanks due to missing codepage tables in the spreadsheet parsing library, likely a build asset inclusion or library initialization issue.

Navigation folder component fails to apply role-based visibility filtering that works at root level, requiring aligned permission guards in folder rendering logic.

Issue body contains only a link to a private issue with no public description or reproduction steps.

Rapid editing in the workflow builder exposes race conditions and state desync across the canvas and persistence layers.

Intermittent real-time update failures with no server errors suggest a cross-cutting problem in the SSE/pub-sub pipeline, browser connection lifecycle, or caching layer that requires deep investigation across frontend, backend, and infrastructure.

The deleted-records view is computing pagination totals against the full record set instead of the filtered deleted set; a localized hook or component fix is needed.

Gmail folder toggle fails to backfill messages because the channel-level sync cursor skips existing history when a new folder is enabled.

Workflow step output mapping passes raw markdown and internal BlockNote structures instead of rendered note content, producing broken notes.

The setup script is missing a documented initialization step, causing fresh environments to fail with missing-relation errors; fix is a localized addition of one command in a single shell script.

Local storage driver omits physical file deletion when attachments or avatars are removed.

Workflow record-update nodes incorrectly permit 'no selected' for non-nullable enum fields, requiring backend validation and frontend option filtering in the workflow builder.

Self-hosted email change confirmation fails silently, likely due to missing email service trigger or misconfigured mail driver in the auth domain.

Auto-generated Note/Task target relations on custom objects incorrectly lock icons and use inconsistent naming compared to standard objects.

Two documented view fields are hardcoded to defaults in the manifest-to-entity converter rather than being mapped from the manifest; requires updating the shared manifest type, converter, and related DTO/entity definitions.

Standard tabs are rendered even after their underlying relations are deleted, indicating a missing existence/filter check in the record layout/tab derivation logic across several frontend components.

The OpenAPI schema incorrectly declares cursor fields as UUID format while the API returns base64-encoded strings; this is a localized schema decorator/fixture change in a shared pagination DTO.

Language switching in the docs site routes to non-existent pages, indicating a localized i18n routing or base-url configuration issue in the documentation site's config.

Email and Calendar tabs crash on custom objects because the UI relation walker cannot traverse join-table paths to Person.

The issue requests new in-app UI and backend mutations to grant/revoke server-level admin rights plus cache invalidation, constituting a cross-cutting feature spanning guards, cache layer, GraphQL resolvers, and React settings pages.

A regression in v1.22.4 prevents the junction-relation UI from rendering target-object selectors, likely caused by a change in how relation metadata or record-field components resolve many-to-many junction displays.

Random Chrome tab crashes during navigation, AI chats, and workspace switching indicate a frontend memory leak or runaway rendering that requires cross-component profiling and architectural fixes.

Inconsistent relative date filtering between quarter and week/month/year indicates buggy date-boundary computation in filter logic.

Read-only workflow permissions incorrectly block execution of active workflows.

The frontend ignores the disabled state of relations and continues to show relation pickers and assignment options that should be hidden.

Two distinct frontend synchronization issues in the demo workspace skill around SSE view-field updates and premature empty view state.

Pivot table layout breaks only when embedded in dashboards, suggesting a container-specific CSS or sizing bug in the dashboard widget renderer.

Worker health probe incorrectly reports an outage despite the process being active.

Select and Multi-Select field types are not mapped into the Zapier integration schema.

Drag-and-drop logic for favorites appears to have an off-by-one boundary error when calculating the drop index for the last position in an active folder.

Infinite scroll threshold is set too low, delaying the fetch of new records until placeholders are already visible.

Localized runtime exception in number field casting utility causes a hard crash on blur/exit.

Updating the workflow trigger causes cascading re-renders across the node, header actions, and side panel, requiring memoization or state-structure changes across several workflow UI files.

Workflow status label in list view derives from a different version snapshot than the detail page.

Workflow update action fails to resolve SELECT field values by user-facing label.

Partial composite LINK updates overwrite unsent sub-fields because the transform lacks a merge-with-existing step.

Generic internal server error on People record mutations with no reproduction steps or logs provided.

App manifest sync resolves widget identifiers correctly for FRONT_COMPONENT but fails to persist the viewId inside FIELDS configuration.