Ensure Proper Transaction Management in Job Handling

[fabrizzio-dotCMS]

Parent Issue

#29474

Task

As a developer, I need to ensure proper transaction management so that the class handling the jobs guarantees that the execution information of each task is saved independently. Each concrete job should have its own transaction handling mechanism, ensuring that if a rollback occurs in a job being executed, it does not interfere with the JobManager.

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

Acceptance Criteria

1. Transaction Management: Implement transaction management in the JobManager class to ensure that the execution information of each task is saved independently.
2. Independent Transactions for Jobs: Ensure each concrete job has its own transaction handling mechanism.
3. Isolation of Rollbacks: Guarantee that a rollback in a specific job does not interfere with the JobManager or other jobs.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[jgambarios]

Closed as this was already done during the development of multiple tickets related to the spike #29474