Change Details

It seems, that sometimes, for maybe various reasons, jobs do not get scheduled and so changes start to accumulated in `wb_changes` table. To clear them out, we need to run the `ResubmitChanges.php` maintenance script regularly. List of tasks about changes being "stuck": * T294008 * T294029 **Acceptance criteria:** * [ ] `ResubmitChanges.php` is run regularly in production resubmitting changes older than 6 hours * [x] Tracking is added for the number of changes that was resubmitted * [x] That tracking data is visible on [edit-dispatching-via-jobs Grafana dashboard](https://grafana.wikimedia.org/d/hGFN2TH7z/edit-dispatching-via-jobs)

It seems, that sometimes, for maybe various reasons, jobs do not get scheduled and so changes start to accumulated in `wb_changes` table. To clear them out, we need to run the `ResubmitChanges.php` maintenance script regularly. List of tasks about changes being "stuck": * T294008 * T294029 **Acceptance criteria:** * [x] `ResubmitChanges.php` is run regularly in production resubmitting changes older than 6 hours * [x] Tracking is added for the number of changes that was resubmitted * [x] That tracking data is visible on [edit-dispatching-via-jobs Grafana dashboard](https://grafana.wikimedia.org/d/hGFN2TH7z/edit-dispatching-via-jobs)

It seems, that sometimes, for maybe various reasons, jobs do not get scheduled and so changes start to accumulated in `wb_changes` table. To clear them out, we need to run the `ResubmitChanges.php` maintenance script regularly. List of tasks about changes being "stuck": * T294008 * T294029 **Acceptance criteria:** * [ * [x] `ResubmitChanges.php` is run regularly in production resubmitting changes older than 6 hours * [x] Tracking is added for the number of changes that was resubmitted * [x] That tracking data is visible on [edit-dispatching-via-jobs Grafana dashboard](https://grafana.wikimedia.org/d/hGFN2TH7z/edit-dispatching-via-jobs)