- data_requests: ein Beschaffungsvorgang je Vorgang mit Modus (automatisch / Freigabe / manuell), getrennten Zählern für Folgefragen und Erinnerungen ohne Rücksetzen, Antwortfrist ≠ Reservierungsfrist. - RequestCaseData: fragt nach, was für das nächste Angebot, die Wunschbestätigung oder (bei verbindlichen Buchungen) administrativ fehlt; ohne E-Mail keine Rückfrage. Teilantwort → gezielte Folgefrage, Schweigen → Erinnerungen, an der Grenze Aufgabe für die Vermieterin. Nie ein Hold. - Mail DataRequested mit Texten nach tatsächlichem Sperrstatus (M11); Dokumentart „Rückfrage“ – im Live-Betrieb ohne Freigabe nur nach Klick. - Signierter, versionierter Ergänzungslink (/angebot/angaben): Lesen schreibt nicht, Absenden über den Fakteneingang, idempotent. - Vorgang: „Rückfrage an den Gast senden“ / „Rückfrage beenden“; Eingangsbestätigung nennt die Klärungsreservierung korrekt. - Zeitplan: cases:data-requests alle fünf Minuten. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
65 lines
2.6 KiB
PHP
65 lines
2.6 KiB
PHP
<?php
|
||
|
||
use App\Actions\AnonymizeGuests;
|
||
use App\Actions\MonitorChannels;
|
||
use App\Actions\RemindChannelTasks;
|
||
use App\Actions\RequestReviews;
|
||
use App\Actions\SendBookingReminders;
|
||
use App\Actions\SendDigests;
|
||
use App\Models\Tenant;
|
||
use App\Tenancy\TenantRunner;
|
||
use Illuminate\Support\Facades\Schedule;
|
||
|
||
/**
|
||
* Everything that acts on a landlord's data runs once per landlord (TenantRunner), so queries see the right
|
||
* rows and mail goes out with the right sender. Only the database backup stays global: one database, one dump.
|
||
*/
|
||
Schedule::command('bookings:expire-holds')->everyFiveMinutes()->withoutOverlapping();
|
||
|
||
Schedule::command('bookings:auto-offers')->everyFiveMinutes()->withoutOverlapping();
|
||
|
||
// v0.11: reminders of data requests (never extends a hold or a deadline of the case).
|
||
Schedule::command('cases:data-requests')->everyFiveMinutes()->withoutOverlapping();
|
||
|
||
Schedule::command('bookings:resend-confirmations')->everyFifteenMinutes()->withoutOverlapping();
|
||
|
||
Schedule::command('channels:sync')->everyFiveMinutes()->withoutOverlapping(10);
|
||
|
||
Schedule::command('channels:fetch-mail')->everyMinute()->withoutOverlapping(5);
|
||
|
||
Schedule::call(fn (TenantRunner $runner, MonitorChannels $monitorChannels) => $runner->each(fn () => $monitorChannels->handle()))
|
||
->name('channels:monitor')
|
||
->everyFifteenMinutes()
|
||
->withoutOverlapping();
|
||
|
||
Schedule::call(fn (TenantRunner $runner, RemindChannelTasks $remindChannelTasks) => $runner->each(fn () => $remindChannelTasks->handle()))
|
||
->name('channels:remind-tasks')
|
||
->everyFifteenMinutes()
|
||
->withoutOverlapping();
|
||
|
||
Schedule::call(fn (TenantRunner $runner, SendDigests $sendDigests) => $runner->each(fn (Tenant $tenant) => $sendDigests->handle($tenant)))
|
||
->name('digests:send')
|
||
->everyFifteenMinutes()
|
||
->withoutOverlapping();
|
||
|
||
Schedule::call(fn (TenantRunner $runner, SendBookingReminders $sendBookingReminders) => $runner->each(fn () => $sendBookingReminders->handle()))
|
||
->name('bookings:reminders')
|
||
->dailyAt('09:00')
|
||
->withoutOverlapping();
|
||
|
||
Schedule::call(fn (TenantRunner $runner, RequestReviews $requestReviews) => $runner->each(fn () => $requestReviews->handle()))
|
||
->name('reviews:request')
|
||
->dailyAt('10:00')
|
||
->withoutOverlapping();
|
||
|
||
Schedule::call(fn (TenantRunner $runner, AnonymizeGuests $anonymizeGuests) => $runner->each(fn () => $anonymizeGuests->handle()))
|
||
->name('guests:anonymize')
|
||
->dailyAt('03:00')
|
||
->withoutOverlapping();
|
||
|
||
// One database, one dump – across all landlords (see MANDANTEN-PLAN §5).
|
||
Schedule::command('backup:database')
|
||
->name('backup:database')
|
||
->dailyAt('02:30')
|
||
->withoutOverlapping();
|