You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When syncing captures from storage, the session regrouping step is buried inside Deployment.save() and not visible as a job stage. Users have no visibility into how many sessions were created/updated, or whether captures were left ungrouped (e.g., due to missing timestamps).
Current behavior
sync_captures() calls self.save(regroup_async=False) which triggers group_images_into_events() internally
The job logs show "Saving and recalculating sessions for deployment" as an INFO message but it's not a tracked stage
If images have NULL timestamps, they silently remain ungrouped with no warning in the job
Desired behavior
Add a "Recalculate sessions" stage to the sync job progress
Show number of sessions created/updated as a stage parameter
Warn if any captures are not assigned to a session (e.g., ungrouped_captures param)
Summary
When syncing captures from storage, the session regrouping step is buried inside
Deployment.save()and not visible as a job stage. Users have no visibility into how many sessions were created/updated, or whether captures were left ungrouped (e.g., due to missing timestamps).Current behavior
sync_captures()callsself.save(regroup_async=False)which triggersgroup_images_into_events()internallyDesired behavior
ungrouped_capturesparam)Related
group_images_into_eventsand may be a good place to implement thisKey code locations
ami/main/models.py:782-851—sync_captures()methodami/main/models.py:979-993—Deployment.save()regroup logicami/main/models.py:1290-1372—group_images_into_events()functionami/jobs/models.py:596-640—DataStorageSyncJobjob type