feat: add developer inactivity alerts#4868
Open
wescopeland wants to merge 4 commits into
Open
Conversation
wescopeland
commented
May 9, 2026
Comment on lines
+148
to
+162
| $schedule->command(UpdateBeatenGamesLeaderboard::class)->everyFiveMinutes(); | ||
|
|
||
| $schedule->command(UpdatePlayerPointsStats::class, ['--existing-only'])->hourly(); | ||
| $schedule->command(UpdateSearchIndexForQueuedEntities::class)->hourly(); | ||
| $schedule->command(ProcessExpiringClaims::class)->hourly(); | ||
|
|
||
| $schedule->command(UpdateAwardsStaticData::class)->everyFourHours(); | ||
|
|
||
| $schedule->command(PruneGameRecentPlayers::class)->daily(); | ||
| $schedule->command(DeleteStalePlayerPointsStatsEntries::class)->weekly(); | ||
| $schedule->command(CheckDeveloperInactivity::class)->daily(); | ||
| $schedule->command(CheckForAchievementSetChanges::class)->daily(); | ||
|
|
||
| if (app()->environment() === 'production') { | ||
| $schedule->command(UpdateAwardsStaticData::class)->everyFourHours(); | ||
| $schedule->command(UpdateBeatenGamesLeaderboard::class)->everyFiveMinutes(); | ||
| $schedule->command(UpdatePlayerPointsStats::class, ['--existing-only'])->hourly(); | ||
| $schedule->command(ProcessExpiringClaims::class)->hourly(); | ||
| $schedule->command(UpdateDeveloperContributionYield::class)->weeklyOn(2, '10:00'); // Tuesdays at 10AM UTC | ||
| $schedule->command(CrawlPlayerWeightedPoints::class)->weeklyOn(3, '10:00'); // Wednesdays at 10AM UTC | ||
| $schedule->command(CheckForAchievementSetChanges::class)->daily(); | ||
| } | ||
| $schedule->command(DeleteStalePlayerPointsStatsEntries::class)->weekly(); | ||
| $schedule->command(UpdateDeveloperContributionYield::class)->weeklyOn(2, '10:00'); // Tuesdays at 10AM UTC | ||
| $schedule->command(CrawlPlayerWeightedPoints::class)->weeklyOn(3, '10:00'); // Wednesdays at 10AM UTC |
Member
Author
There was a problem hiding this comment.
Sorted these around and removed the production conditional on several of them (no longer needed now that we have a dedicated stage server).
Member
There was a problem hiding this comment.
I assumed the environment check was so they don't run in the local environment. I hadn't really considered not wanting to run them in stage.
Member
Author
There was a problem hiding this comment.
Yep, purely here as a guard against stage.
These shouldn't ever run locally. On our app server, we have a cron that runs every 60 seconds:
php artisan schedule:run
This Laravel built-in command checks if there are any scheduled commands that are due for execution and executes what's ready to go.
Jamiras
reviewed
May 10, 2026
Comment on lines
+148
to
+162
| $schedule->command(UpdateBeatenGamesLeaderboard::class)->everyFiveMinutes(); | ||
|
|
||
| $schedule->command(UpdatePlayerPointsStats::class, ['--existing-only'])->hourly(); | ||
| $schedule->command(UpdateSearchIndexForQueuedEntities::class)->hourly(); | ||
| $schedule->command(ProcessExpiringClaims::class)->hourly(); | ||
|
|
||
| $schedule->command(UpdateAwardsStaticData::class)->everyFourHours(); | ||
|
|
||
| $schedule->command(PruneGameRecentPlayers::class)->daily(); | ||
| $schedule->command(DeleteStalePlayerPointsStatsEntries::class)->weekly(); | ||
| $schedule->command(CheckDeveloperInactivity::class)->daily(); | ||
| $schedule->command(CheckForAchievementSetChanges::class)->daily(); | ||
|
|
||
| if (app()->environment() === 'production') { | ||
| $schedule->command(UpdateAwardsStaticData::class)->everyFourHours(); | ||
| $schedule->command(UpdateBeatenGamesLeaderboard::class)->everyFiveMinutes(); | ||
| $schedule->command(UpdatePlayerPointsStats::class, ['--existing-only'])->hourly(); | ||
| $schedule->command(ProcessExpiringClaims::class)->hourly(); | ||
| $schedule->command(UpdateDeveloperContributionYield::class)->weeklyOn(2, '10:00'); // Tuesdays at 10AM UTC | ||
| $schedule->command(CrawlPlayerWeightedPoints::class)->weeklyOn(3, '10:00'); // Wednesdays at 10AM UTC | ||
| $schedule->command(CheckForAchievementSetChanges::class)->daily(); | ||
| } | ||
| $schedule->command(DeleteStalePlayerPointsStatsEntries::class)->weekly(); | ||
| $schedule->command(UpdateDeveloperContributionYield::class)->weeklyOn(2, '10:00'); // Tuesdays at 10AM UTC | ||
| $schedule->command(CrawlPlayerWeightedPoints::class)->weeklyOn(3, '10:00'); // Wednesdays at 10AM UTC |
Member
There was a problem hiding this comment.
I assumed the environment check was so they don't run in the local environment. I hadn't really considered not wanting to run them in stage.
Jamiras
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://discord.com/channels/476211979464343552/1002688331827658774/1498772708413149294
This PR adds support for surfacing developer inactivity alerts into a Discord feed channel. Users with a junior developer, moderator, or admin role are excluded from this check.
The alert checks for:
users.last_updated_at)If the developer is site-inactive for 3 months, an alert will surface. If the developer doesn't have any of the above activities recorded for 6 months, an alert will surface.
The alerts are driven by a nightly scheduled command. Results are cached in Redis so the same alert doesn't pop multiple times.