Feature Request: Event after export is fully stored on disk

[Kristories]

Currently, there is no event that fires after the export file has been completely written to disk.

When using chunks or queued exports (as described in the documentation), the AfterSheet event is triggered multiple times — once per chunk — which makes it unsuitable for logic that should only run once after the final file is ready.

Example use case

A common scenario is sending a notification to the user once the exported file is ready for download. With the current events, there is no reliable way to know when the file has actually been stored.

It’s often suggested to use ->chain() after queue(). However, this also results in multiple executions when the export is processed in chunks. In other words, the chained job will fire multiple times, not once at the end of the entire export.

 (new SpkExport($resources, $user))
    ->queue($filename, $disk, Excel::XLSX)
    ->chain([new Notify($user, $filename, $disk)]);

Proposal

Introduce a new event (e.g. AfterExportStored) or alternatively, allow an explicit success() callback similar to the existing failed() method, that is dispatched once the export has fully completed and the file exists on disk, regardless of chunking or queued processing. This would provide a clean, reliable hook for post-processing tasks like sending download links or updating export statuses.

class ExportReport implements FromQuery, WithEvents
{
    public function registerEvents(): array
    {
        return [
            AfterExportStored::class => function(AfterExportStored $event) {
                // File is now guaranteed to exist on disk
                $path = $event->path;     // e.g. "exports/report.xlsx"
                $disk = $event->disk;     // e.g. "s3"

                // Example: notify user that download is ready
                Notification::route('mail', '[email protected]')
                    ->notify(new \App\Notifications\DownloadReady($path, $disk));
            },
        ];
    }
}

class ExportReport implements FromQuery
{
    public function success($event)
    {
        // File is now guaranteed to exist on disk
        $path = $event->path;     // e.g. "exports/report.xlsx"
        $disk = $event->disk;     // e.g. "s3"

        // Example: notify user that download is ready
        Notification::route('mail', '[email protected]')
            ->notify(new \App\Notifications\DownloadReady($path, $disk));
    }
}

[patrickbrouwers]

You can chain a job to the export

[Kristories]

It’s often suggested to use ->chain() after queue(). However, this also results in multiple executions when the export is processed in chunks. In other words, the chained job will fire multiple times, not once at the end of the entire export.

 (new SpkExport($resources, $user))
            ->queue($filename, $disk, Excel::XLSX)
            ->chain([new Notify($user, $filename, $disk)]);