Project

General

Profile

Actions

Bug #22129

closed

Id to start looking for report json should not be zero but highest id causing abysmal performance on postgresql

Added by Vincent MEMBRÉ over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Campaigns
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

Since we don't update the starting value when we don't get any report_json, next run will use the same id to check for new reports, but we should use store the highest id in databse instead


Subtasks 1 (0 open1 closed)

Bug #22144: Highest id only fetch at first run, but batch is runningReleasedFrançois ARMANDActions
Actions

Also available in: Atom PDF