Roos-fs-ZIP

The root cause is that the job can be enqueued multiple times in certain scenarios:

1. The transaction is not yet committed, and complete! is called multiple times (for example, due to a frontend bug or double-click).
2. The object is saved multiple times within a single transaction, causing the after_commit or after_save callbacks to trigger multiple job enqueues (rare cases).

Environment:

OS: Windows 11 Version 24H2 for x64-based systems(KB5065426) (26100.6584)

Browser: Chrome 140.0.7339.186 (Official Build) (64-bit)

Platform: Desktop

Executor: Tretjacova Olena

Preconditions:

1. The 'Services' page is opened.
2. Click on the button '+Create New Service'
3. 'New Service' page is opened.
4. Select 'OIL CHANGE TEMPLATE' in the Select Template section.
5. Select 'OLENA098765432112' in the Assignment Vehicle section.
6. Click 'Create Service'.
7. The service was created.
8. Open the 'Services' page.
9. Click the view icon next 'OIL CHANGE TEMPLATE' service in the table.
10. The Service Detail page is opened.
11. Pass the steps to complete the service.

Steps:

1. Open the Services page.
2. Click the 'Export Completition Reports'
3. Select Start Date and End Date : 09/29/2025.
4. Select Customer : 'Tretyjacova-company'.
5. Select Vehicle : OLENA098765432112.
6. Select PDF Report in Export Type section.
7. Click 'Download Reports' button.

Expected Result:

One PDF report in EN is downloaded.
One PDF report in DE is downloaded.

Actual Result:

Two PDF report in DE is downloaded.
Two PDF report in EN is downloaded.

Attachment:

https://screenrec.com/share/YnINv3RrlH

Rechecking the issues with another ID service (5924) showed that only one EN and one DE report were downloaded, and I got a negative result because the service in the previous test was conducted twice.