https://sonarly.com/issue/3881?type=bug
The v1.19.0 release introduced the `messageChannelMessageAssociationMessageFolder` standard object and code that unconditionally uses it during message import, but workspaces that haven't run the 1.19 upgrade migration command lack this object metadata, causing message import to fail.
Fix: Added a guard in both `MessagingMessageFolderAssociationService` and `MessagingDeleteFolderMessagesService` to check if the `messageChannelMessageAssociationMessageFolder` object exists in the workspace's metadata before attempting to get its repository.
The check uses `getWorkspaceContext().objectIdByNameSingular` (already populated by `executeInWorkspaceContext`) to verify the object is present. If not (workspace hasn't run the 1.19 upgrade migration), the code gracefully skips the folder association operations instead of throwing a `MALFORMED_METADATA` error.
This is the correct fix because:
1. The `messageChannelMessageAssociationMessageFolder` object is new in v1.19.0 and requires a per-workspace backfill migration
2. The message import worker runs immediately after deployment, before all workspaces are migrated
3. Skipping is safe — un-migrated workspaces have no folder associations to read/write, and will get full functionality once the upgrade command runs
Sonarly Claude Code
e5c592ccf6