Permanent API errors (401, 403, etc.) silently succeed in workpool logs

[agucova]

Problem

When the Resend API returns a permanent error (e.g., 401 Unauthorized due to an invalid API key), the error is recorded in the component's internal email table via markEmailsFailed, but the workpool action returns without throwing (line 559 of src/component/lib.ts):

if (PERMANENT_ERROR_CODES.has(response.status)) {
  // report the error to the user
  await ctx.runMutation(internal.lib.markEmailsFailed, {
    emailIds: args.emails,
    errorMessage: `Resend API error: ${response.status} ${response.statusText} ${await response.text()}`,
  });
  return; // ← returns successfully, workpool counts this as "succeeded"
}

This means:

1. The workpool reports succeeded: N, failed: 0 — giving the impression emails were sent
2. No error appears in Convex function logs
3. The only way to discover the failure is to query the component's internal email status via resend.status(ctx, emailId), which most users won't do proactively

We hit this in production with an expired API key. The Convex logs showed succeeded: 1 for every magic link email attempt, and it took significant debugging to discover that no emails were actually being delivered. The Resend dashboard showed zero emails sent.

Expected behavior

At minimum, permanent API errors should be logged to the Convex function logs (e.g., console.error) so they're visible in the dashboard. Ideally, they should also cause the workpool job to be reported as failed.

Environment

• @convex-dev/resend: v0.2.3
• Convex deployment: cloud
• Error code encountered: 401 (invalid API key)

[ianmacartney]

Good callout - want to put up a PR to do that logging?

…

On Sun, Feb 8, 2026 at 5:09 PM Agustín Covarrubias ***@***.***> wrote: *agucova* created an issue (get-convex/resend#71) <#71> Problem When the Resend API returns a permanent error (e.g., 401 Unauthorized due to an invalid API key), the error is recorded in the component's internal email table via markEmailsFailed, but the workpool action *returns without throwing* (line 559 of src/component/lib.ts): if (PERMANENT_ERROR_CODES.has(response.status)) { // report the error to the user await ctx.runMutation(internal.lib.markEmailsFailed, { emailIds: args.emails, errorMessage: `Resend API error: ${response.status} ${response.statusText} ${await response.text()}`, }); return; // ← returns successfully, workpool counts this as "succeeded"} This means: 1. The workpool reports succeeded: N, failed: 0 — giving the impression emails were sent 2. No error appears in Convex function logs 3. The only way to discover the failure is to query the component's internal email status via resend.status(ctx, emailId), which most users won't do proactively We hit this in production with an expired API key. The Convex logs showed succeeded: 1 for every magic link email attempt, and it took significant debugging to discover that no emails were actually being delivered. The Resend dashboard showed zero emails sent. Expected behavior At minimum, permanent API errors should be logged to the Convex function logs (e.g., console.error) so they're visible in the dashboard. Ideally, they should also cause the workpool job to be reported as failed. Suggested fix Add a console.error before the early return: if (PERMANENT_ERROR_CODES.has(response.status)) { const errorText = await response.text(); const errorMessage = `Resend API error: ${response.status} ${response.statusText} ${errorText}`; console.error(errorMessage); await ctx.runMutation(internal.lib.markEmailsFailed, { emailIds: args.emails, errorMessage, }); return;} Environment - @convex-dev/resend version: see lockfile (latest as of Feb 2026) - Convex deployment: cloud - Error code encountered: 401 (invalid API key) — Reply to this email directly, view it on GitHub <#71>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACZQW4HGEPVHMJ76OJQ7DL4K7M5BAVCNFSM6AAAAACUNNQI4CVHI2DSMVQWIX3LMV43ASLTON2WKOZTHEYTGOJXHE3DENQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>