Export Actions using Amazon S3 creates millions of Queue Invocations

[nelsonmelecio]

Package

filament/filament

Package Version

v3.2.33

Laravel Version

v10.43.0

Livewire Version

v3.4.4

PHP Version

PHP 8.2.10

Problem description

What we did:

• We have a table with 100k+ records.
• Implemented Export Actions to CSV Ref: https://filamentphp.com/docs/3.x/actions/prebuilt-actions/export
• Set filedisk to S3

The issue:

• Once the CSV export is triggered, it creates millions of Queue Invocations. See image below:
• And so as the jobs
• generated a bunch of CSVs

Not sure if this is the expected behaviors when pointing the export features to use Amazon S3.

It works fine when using local storage.

Expected behavior

It should create only one CSV when exporting and should only use countable jobs/queues I guess?

Steps to reproduce

1. Create a filament panel with list of records that are more than 100k records
2. Implement Export Actions and point to S3
3. Check the generated files, the jobs/queues.

Reproduction repository

n/a

Relevant log output

n/a

[github-actions[bot]]

Hey @nelsonmelecio! We're sorry to hear that you've hit this issue. 💛

However, it looks like you forgot to fill in the reproduction repository URL. Can you edit your original post and then we'll look at your issue?

We need a public GitHub repository which contains a Laravel app with the minimal amount of Filament code to reproduce the problem. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private / confidential, since we want a link to a separate, isolated reproduction. That would allow us to download it and review your bug much easier, so it can be fixed quicker. Please make sure to include a database seeder with everything we need to set the app up quickly.

[nelsonmelecio]

Please understand that I don't want to recreate this since it may transfer millions of files again in our S3 accounts. So I will set the Reproduction repository empty for now.

[nelsonmelecio]

cc: @danharrin @zepfietje @ryangjchandler Please kindly check this issue.

[danharrin]

Please create a repository, even if you only run it locally and not on S3. I want to check your configuration

There should be job for each chunk

[danharrin]

The multiple CSVs are correct, there is one for each chunk, and they get combined when downloaded