User with many relationships, loop within Job class

In the job, I'd just create a query that

1. gets users who do not have a tenency
2. where last tenancy date = now()->subDays(21)

Then just build up your email(s) to admin based on the result(s) and queue it/them.

It really depends on how you store everything. You might just be able to use a has() on the belongsTo relationship and where last tenancy date is 21 days in the past.

@Cronix Thanks for a good shout, but I'm getting the following error now:

In HasRelationships.php line 555:

  Allowed memory size of 134217728 bytes exhausted (tried to allocate 266240
  bytes)

This is based on the following within the job class.

$user = User::has('tenancies')->get();
foreach($user as $u) {
            \Log::info($u);
}

Are your users being logged? Can you determine if the error occurs before, during, or after fetching the users?

During the loop, the bytes exhausted error occurs.

Try to determine if it happens when handling a particular user or if it happens after a certain amount of users.

$user = User::has('tenancies')->inRandomOrder()->get();
foreach($user as $index => $u) {
    \Log::info($index . ' : ' . $u->id);
    \Log::info($u);
}

@36864 - I'm still getting:

local.ERROR: App\Jobs\CheckVerificationStatus has been attempted too many times or run too long. The job may have previously timed out.

still

That's the first time you've mentioned that error in this thread.

The error is pretty self-descriptive, your job is currently marked as having too many tries. Clear your job queue and re-queue the job.

Still as in its still bytes exhausted sort of error.

Job queue is clear and failed jobs table is also clear now, so will try again,

Which now also seems to working, I can see the output within the log file.

My post did nothing to help with your original question, it only helped you debug an unrelated issue. Please mark an accepted answer based on the topic of this thread so people who land here after searching for a related problem aren't confused.

Yes your post helped debug the issue, but also you mentioned the key => value within the loop so I see that as a valid answer.