Changed the error logging in `FilesFieldDeletionJob` from `logger.log` (info level) to `logger.error` with full stack trace.
Previously, when file deletion failed in the background job, the error was silently swallowed with an info-level log message (`this.logger.log('Failed to delete file ...')`), making it invisible in production monitoring. The caught error object was also discarded entirely, losing the stack trace and root cause details.
Now the job logs at error level with the workspace ID for context and includes the full stack trace, making file deletion failures detectable by log-based alerting (Sentry, Datadog, etc.).
Sonarly Claude Code
fbf8e5bef9