### Work Function Not Found Error During rolling upgrades or version rollbacks, background migration jobs may temporarily log a work function not found error when some worker pods lack the required function code as the rollout proceeds. This transient error is currently being reported to Sentry via `errorreporting.Capture()` in the `FindJob` method, causing noise during deployments when the BBM is released alongside the work function in the same release. ### Solution The fix is to prevent transient errors (specifically "Work Function Not Found" errors with `InvalidJobSignatureBBMErrCode`) from being reported to Sentry. ### Implementation Suggestion : This can be achieved by moving the `errorreporting.Capture(ctx, err)` call in the `FindJob` method to occur **only after** checking if the error is transient. **Location**: `registry/bbm/bbm.go` - `FindJob` method (around lines 500-510) **Current behavior**: All validation errors are reported to Sentry immediately, including transient ones. **Required change**: Only report permanent validation errors to Sentry. Transient errors (those with `InvalidJobSignatureBBMErrCode`) should be logged but not reported to Sentry.