Skip to content

Commit ab3bd3c

Browse files
fix(backend): log failedReason when connection sync job fails
The error message from a failed connection sync job was being stored in the DB but never surfaced in the logs, making it impossible to diagnose failures without querying the database directly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent ca63bf2 commit ab3bd3c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

packages/backend/src/connectionManager.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -378,7 +378,7 @@ export class ConnectionManager {
378378
this.promClient.activeConnectionSyncJobs.dec({ connection: connection.name });
379379
this.promClient.connectionSyncJobFailTotal.inc({ connection: connection.name });
380380

381-
jobLogger.error(`Failed job ${job.id} for connection ${connection.name} (id: ${connection.id}). Failing job.`);
381+
jobLogger.error(`Failed job ${job.id} for connection ${connection.name} (id: ${connection.id}). Reason: ${job.failedReason}`);
382382

383383
const config = connection.config as unknown as ConnectionConfig;
384384
captureEvent('backend_connection_sync_job_failed', {

0 commit comments

Comments
 (0)