Struggling with a weird laravel framework issue related to queued jobs failing silently after deployment?

hey everyone, we're working on 'Laravel Quick Fix & Consultation' for clients and recently hit a snag with our own internal app. it's a bit embarrassing, hah. basically, some of our queued jobs, which handle external API calls and some data processing, just silently fail sometimes. there's no explicit errors in the main laravel logs, just... nothing happens after a while. it's a real laravel framework issue that's been super hard to pin down, making our laravel development a bit frustrating right now.

we've checked supervisor logs, increased job timeouts in the config, even tried different queue drivers like redis and database to rule out driver-specific issues. server resources are totally fine, no memory limits being hit, and other jobs run perfectly. the problem is super intermittent, which makes it a nightmare to debug. sometimes a job runs fine, other times it just vanishes into thin air. it's like the process just exits without a trace.

here's a dummy log snippet of what we sometimes see in supervisor logs when it happens (or often, nothing at all):

[2023-10-27 10:35:01] Process 12345 exited with status 0\n[2023-10-27 10:35:01] Starting new supervisor worker

what are some advanced debugging techniques or common misconfigurations for these kinds of silent failures in Laravel queues that might not show up as typical exceptions? we're really scratching our heads here. waiting for an expert reply!