[EXCONTRANS-314] maxAttempts per item is not reseted for each execution of a job Created: 25/Mar/19  Updated: 24/Mar/20  Resolved: 07/Oct/19

Status: Closed
Project: Content Translation Extended (CTX)
Component/s: None
Affects Version/s: 2.0.3
Fix Version/s: 3.0, 2.9

Type: Improvement Priority: Major
Reporter: Mercedes Iruela Assignee: Adrien Manzoni
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
is related to EXCONTRANS-316 All requests are for the same language Resolved
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Once the batch is submitted the cron job will start trying to retrieve the translation. If the translation is immediately available it will be retrieved. If it's not immediately available the cron job will run as scheduled. Eventually, the max number of attempts will be reached and the cron job will stop trying to retrieve the translation. maxAttempt value in the item is never resetted.

For example, if maxAttempt is set to 100 and the cron is set to run at 6am and then 6pm each day the max number of attempts will be reached at 6am, as the scheduler keeps running until the maxAttempt limit is reached. When the script runs again at 6pm it won't attempt to retrieve the file, since the maxAttempts value for the item was already reached. This means that if the file is delivered between these two times it won't be retrieved.

maxAttempts value for each item should be reset each time the job runs.



 Comments   
Comment by Adrien Manzoni [ 07/Oct/19 ]

Issue resolved in the 2.9 (M5) and 3.0(M6)

Generated at Mon Feb 12 00:30:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.