Fixed
Details
Priority
MinorAssignee
AlexAlexReporter
AlexAlexDeveloper
AlexAlexReviewer
Erik S.Erik S.Change Log Group
FixedChange Log Message
Fixed case, when scheduled task might have executed more times, then expected by it's run schedule.Patch Instructions
Patches must be submitted through Phabricator.
To submit patch via Command Line use Patches Workflow (via Arcanist) tutorial.
To submit patch via Web Interface use Patches Workflow (via Web Interface) tutorial.
Time tracking
1h 30m loggedStory Points
1Original estimate
Fix versions
Details
Details
Priority
Assignee
Alex
AlexReporter
Alex
AlexDeveloper
Alex
AlexReviewer
Erik S.
Erik S.Change Log Group
Fixed
Change Log Message
Fixed case, when scheduled task might have executed more times, then expected by it's run schedule.
Patch Instructions
Patches must be submitted through Phabricator.
To submit patch via Command Line use Patches Workflow (via Arcanist) tutorial.
To submit patch via Web Interface use Patches Workflow (via Web Interface) tutorial.
Time tracking
Story Points
1
Original estimate
Fix versions
Created November 6, 2018 at 10:40 AM
Updated December 29, 2024 at 8:49 PM
Resolved January 11, 2021 at 8:57 AM
In the "\kScheduledTaskManager::runAll" method, when iterating over "$events_source" array and after site domain limitation was checked:
query "LastRunOn" column value of current scheduled task from database
if it doesn't match "$event_data['LastRunOn']" (means parallel process already executed it and update the date), then continue to next scheduled task