ER: Bug fix for "Schedule Monthly" workflow

[t-will-gillis]

Emergent Requirement - Problem

The 12/1/25 run of the "Schedule Monthly" workflow did not work as expected in two areas:

• First, on the message posted to the Monday agenda, the bot incorrectly listed four devs and their Skills Issues as "Non-team members with open issues." The bot had just removed those four from the website-write team and closed their Skills Issues.
• Second, the bot closed the wrong issue: Reopen Issues Without Linked PR #8438 was closed instead of the intended Review Inactive Team Members #8439.

Issue you discovered this emergent requirement in

• Review Inactive Team Members #8439

Date discovered

12/1/25

Did you have to do something temporarily

• YES
• NO

Who was involved

@t-will-gillis

What happens if this is not addressed

The same errosr could recur.

Resources

https://github.com/hackforla/website/blob/gh-pages/.github/workflows/schedule-monthly.yml
https://github.com/hackforla/website/blob/gh-pages/.github/workflows/wr-schedule-monthly.yml
https://github.com/hackforla/website/blob/gh-pages/github-actions/trigger-schedule/list-inactive-members/trim-inactive-members.js

Recommended Action Items

• Make a new issue
• Discuss with team
• Let a Team Lead know

Potential solutions [draft]

• Note that although this ER is listed as Complexity: Medium, the actual issue to fix the bugs should be Complexity: Large.
• For the first error, in trim-inactive-members.js the error can be traced to the check for getOpenAssignedIssues() running before the previous function removeInactiveMembers() was completed. One solution might be to add a delay before the "Final check..." around line 52, or otherwise ensure that all preceding functions have completed before running getOpenAssignedIssues().
• Similarly for the second error, in the workflow run wr-schedule-monthly.yml, the "Get issue number" step likely ran before the issue was created by the schedule-monthly.yml workflow despite the trigger if: ${{ github.event.workflow_run.conclusion == 'success' }}. The solution might be to add a delay either to the WR yml or a promise to the schedule-monthly.yml workflow.