Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
[Maintenance] - Slack Delayed Meeting Message
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
Slack Meeting message notifications are arriving after the meeting is scheduled.

Acceptance Criteria
- Around 5-10 meeting tests pass rigorous inspection ensuring the issue doesn't occur again
- A reason is found and can be explained as to why this is happening
Proposed Solution
- Try to reproduce it (Schedule a meeting 10 minutes from now and SWITCH YOUR OUTPUT TO PRINT IN CONSOLE INSTEAD OF SENDING A MEETING NOTIFICATION. Please try not to spam the main software channel. If you do accidentally, don't worry, but try not to.)
- Figure out if it is a rare occurrence. If so, try your best to pinpoint what might be causing it (whether if it is a code error or an environment error. Sometimes it might just be as simple as the environment accidentally has a different timezone when the cron/batch job runs).
- Remember, if you can't find why it's happening, you cannot finish this ticket. Most of this ticket will be trying to find out why it is happening.
Mocks
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the delayed Slack meeting notification with output redirected to the console, as described in the issue, while avoiding the main software channel. Then inspect the meeting scheduling and notification flow for timing or environment-related causes, including timezone behavior. Done means the cause is explained and roughly 5–10 meeting tests pass without reproducing the delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100