Activity Tab continues to track and display user edits after Course End Date

[Formasitchijoh]

What is happening?

Activity Tab continues to display users real-time Wikipedia contributions long after a course has officially ended. While the primary course statistics (Words Added, Articles Created) correctly stop at the "End Date," the Activity feed does not. Example program

https://outreachdashboard.wmflabs.org/courses/Cin%C3%A9ma_Municipal_Le_Cosmos/r%C3%A9alisatrices_et_actrices_afro-descendantes_germanophones_avec_Noircir_Wiki_(dimanche_9_novembre_2025)/activity/recent

The Problem:
Participants expect that once a course tracking period ends, the Dashboard will stop publicizing their wiki activity. Currently, the Activity tab fetches all recent edits via the API regardless of the course's timeframe. This creates a privacy concern where organizers/public can monitor a user's post-event activity indefinitely.

Expected behavior

The Activity feed should strictly stop displaying new contributions 7 days after the course end date to align with the standard data-fetching buffer

[AarohiSharma5]

Hi @Formasitchijoh, I would like to investigate this issue.

[AarohiSharma5]

Hi @Formasitchijoh, I think the function responsible for this, is this one:

"const fetchAllRevisions = async (API_URL, days, usernames, wiki, course_start, last_date) => {
let ucend;
let exitNext = false;
if (isBefore(subDays(toDate(last_date), days), toDate(course_start))) {
ucend = formatISO(toDate(course_start));
exitNext = true;
} else if (isBefore(subDays(toDate(last_date), days), subYears(new Date(), 5))) {
ucend = formatISO(subYears(new Date(), 5));
exitNext = true;
} else {
ucend = formatISO(subDays(toDate(last_date), days));
}"

present in the mediawiki_revisions_utils.js.
There is no constraints to decide the "last_date" in relation with the "course_end", which creates the issue. It considers the last date with no connection with the course_end date. Hence, fetches all the data on the way according to the conditions present(like, 5 years before the clock). I think of adding parameters like this course_end in the function, and then adding a conditional statement checking if the data is within the range(i.e. 7 days after the course ends). What do you think about this approach?