Migrate remaining rate-limit error message usages to throttled_error_message

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

Summary

Gitlab::ApplicationRateLimiter.throttled_error_message was introduced in !245757 (merged) as a common method to be used when responding with a rate limit error. There's several references that still use the string directly, and as part of this refactor we need to update those.

Improvements

Using the same string across the codebase, and preventing drift in responses based on where its sent from.

Risks

The corresponding call site could break if the common method reference cant be reached

Involved components

References found in 16 call sites across 15 files (as of Aug 21 2026)

• app/controllers/concerns/check_rate_limit.rb:15
• app/controllers/import/gitlab_groups_controller.rb:64
• app/controllers/onboarding/feature_library_controller.rb:70
• app/controllers/onboarding/feature_library_controller.rb:77
• app/controllers/projects/settings/integrations_controller.rb:158
• app/graphql/mutations/import/source_users/resend_notification.rb:38
• app/services/concerns/rate_limited_service.rb:41
• app/services/import/github_service.rb:13
• lib/api/helpers/rate_limiter.rb:19
• app/graphql/mutations/notes/create/base.rb:65
• app/graphql/mutations/todos/delete_all_done.rb:33
• app/graphql/mutations/todos/delete_many.rb:36
• ee/app/graphql/mutations/ai/action.rb:160
• ee/app/graphql/resolvers/package_metadata/advisories_resolver.rb:54
• ee/app/graphql/resolvers/package_metadata/advisory_resolver.rb:38

Optional: Intended side effects

Optional: Missing test coverage