Opening/visiting work not always sufficient to add work to History

Description

This issue cannot be consistently reproduced, but when it occurs, the process is as follows:

1. Load work URL via HTML link while logged into user account
2. Navigate away from page/close browser
3. Return later to user account History to find the work is not listed.

This is different from/in addition to the delay experienced occasionally between accessing a work and the work showing up in the account history. There is no evident or reported pattern of behavior/commonalities in works that aren't added to the History.

A current workaround for this issue is to select the Mark For Later button, and then select the Mark as Read button, which seems to force the History to update and will include the work in the History.

Activity

Show:
Sarken
July 5, 2017, 6:06 AM

james_ [16:06]
There are some things I would do to make it more reliable.

[16:06]
( But I don't know if there are approaching the issue from the right way )

[16:07]
It's possible that sometimes the periodic class hits an error so that a whole chunk of history gets discarded.

[16:08]
So I would move it to a scheduled task and add some exception handling.

Lady Oscar [16:08]
A whole chunk of the user’s history, or a whole chunk of “history saving everywhere on the Archive”?

james_ [16:08]
I would expect it to be say a 10 minute chunk for all people in a rare case.

Lady Oscar [16:08]
That sounds like it could be this, then

james_ [16:08]
or 1,000 records if we do chunking.

[16:09]
Most people wouldn't notice if we lost a couple of 1,000 readings in a day.

Assignee

Unassigned

Reporter

coaldustcanary

Roadmap

Reading History

Priority

Low

Affects versions

Fix versions

None

Components

BackEnd

Difficulty

Medium

Milestone

Internal 0.9