Background job runs twice

Add locking or idempotency checks around side effects.

How to troubleshoot

1. Reproduce the issue with non-sensitive test data and record the expected versus actual result.
2. Add locking or idempotency checks around side effects.
3. Test the fix in staging, check logs, and deploy with a rollback plan.

When to get professional assistance

If these steps do not resolve the issue, or you suspect failing hardware, data loss, a security incident, or a production-system problem, consider qualified technical support. Back up important data where possible and obtain authorization before changing business systems.

← Return to the Help Center