SSWConsulting / SSWConsulting/SSW.Tiger
🐛 Tiger morning meetings failing (job executions failing)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 2
Description
Cc: @yaqi-lyu @calumjs @joshbermanssw @suiyangqiu
Hi Team!
Pain
Tiger morning meetings appear to have failed (report suggests all morning Tiger meetings failed for an unknown reason), impacting the team’s ability to run scheduled meetings.
Acceptance Criteria
- Tiger morning meetings run successfully for the intended schedule.
- Any failing scheduled meeting/job run is detectable via monitoring/alerting and has actionable logs.
Reproduce Steps
- Open the Tiger scheduling/execution system.
- Review the morning meeting runs for today.
- Observe failures in the execution history.
- See error.
Screenshot
Figure: Azure portal showing Container App Job job-tiger-staging execution history with multiple failed runs
Thanks!
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 with the Azure portal Container App job job-tiger-staging execution history and review today’s failed morning meeting runs. Inspect the reported error and any existing monitoring or logs. Done means the intended scheduled meetings run successfully, while failed runs are detected with actionable logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript
- Domain
- backend, cloud, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100