Add automatic retry for serializable transaction failures

[fractaledmind]

• Add AcidicJob. initialize_workflow_max_retries config (default: 3)
• Add InitializeWorkflowRetriesExhaustedError
• Extract find_or_create_execution method with built-in retry logic
• Catch ActiveRecord::SerializationFailure and ActiveRecord::Deadlocked
• Implement exponential backoff (50ms, 100ms, 200ms, etc.)

Resolves #91

[Copilot]

Pull request overview

This PR implements automatic retry logic for serializable transaction failures when initializing AcidicJob workflows. The feature addresses a known issue where serializable transactions can fail transiently due to concurrent access, requiring automatic retry handling.

Changes:

• Added configurable max retries with exponential backoff for serializable transaction failures
• Extracted workflow initialization logic into a new private method with built-in retry handling
• Added comprehensive test coverage for retry scenarios including success after retries, exhausted retries, and deadlock handling

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
lib/acidic_job.rb	Adds new configuration option initialize_workflow_max_retries with default value of 3
lib/acidic_job/errors.rb	Introduces InitializeWorkflowRetriesExhaustedError exception for when retry attempts are exhausted
lib/acidic_job/workflow.rb	Refactors transaction logic into find_or_create_execution method with retry handling for SerializationFailure and Deadlocked exceptions using exponential backoff (50ms, 100ms, 200ms, etc.)
test/acidic_job/workflow_errors_test.rb	Adds four comprehensive tests covering serialization failure retry success, retry exhaustion, deadlock retry success, and configurable retry limits

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.