Skip to content

Add rate limiting to scheduler tick endpoint (issue #474)#589

Closed
anshul23102 wants to merge 1 commit into
utksh1:mainfrom
anshul23102:fix/issue-474-scheduler-rate-limit
Closed

Add rate limiting to scheduler tick endpoint (issue #474)#589
anshul23102 wants to merge 1 commit into
utksh1:mainfrom
anshul23102:fix/issue-474-scheduler-rate-limit

Conversation

@anshul23102
Copy link
Copy Markdown
Contributor

Fixes #474: Implemented rate limiting on POST /api/v1/workflows/scheduler/tick.

Changes:

  • 5 requests per minute limit per user
  • 429 Too Many Requests response
  • RateLimiter class for throttling
  • Prevents scheduler tick abuse

Protects scheduler from being overwhelmed by repeated requests.

Issue utksh1#474: POST /api/v1/workflows/scheduler/tick had no rate limiter,
allowing any authenticated caller to trigger unlimited scheduler ticks.

Changes:
- Created RateLimiter class for request throttling
- Limited scheduler endpoint to 5 requests per minute per user
- 429 Too Many Requests response when limit exceeded
- Automatic request cleanup to prevent memory leaks

Fixes utksh1#474
@anshul23102
Copy link
Copy Markdown
Contributor Author

Closed - will create proper professional PR

@anshul23102 anshul23102 closed this Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: POST /api/v1/workflows/scheduler/tick has no rate limiter, allowing any authenticated caller to trigger unlimited scheduler ticks

1 participant