### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 24, 2026, 2:56pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/3 "2026-07-24T14:56:36Z")
Can you help me to understand how the fix works? I see the translation key in server.en.yml and the `override_key` have been renamed to match the name of the check. I wonder why both needed to be renamed to match the name of the file. Shouldn’t it also have worked with `sidekiq` instead of `sidekiq_check`? I wonder if it’s still the name of the check instead of the override\_key that influences which warning is shown, so I wonder if the override `dashboard.problem.queue_size` works or if that is a text that is never shown just like `dashboard.problem.sidekiq` was not.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [July 24, 2026, 3:33pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/4 "2026-07-24T15:33:09Z")
Yes, we refer in a separate file to the problem check identifier:
>
So the PR above makes sure that the string in the translations matches the problem check filename, which is converted to that identifier, i.e. `sidekiq_check`. Using `sidekiq` in the translation strings wasn’t working, it wasn’t matching the identifier.
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 24, 2026, 4:24pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/5 "2026-07-24T16:24:30Z")
> [@pmusaraj](#):
>
> So the PR above makes sure that the string in the translations matches the problem check filename, which is converted to that identifier, i.e. `sidekiq_check`. Using `sidekiq` in the translation strings wasn’t working, it wasn’t matching the identifier.
Sorry, I still don’t really understand.
`queue_size` doesn’t match the filename/identifier either, just like `sidekiq` did not. And I still don’t understand why this isn’t a problem in that case.
Is this because there is another code path that directly uses the identifier instead of one of the override keys? So instead of adding a third translation key matching the filename, you changed `sidekiq` to use the identifier-based key? Kind of a two-in-one solution supporting both the override case and the identifier case?
If so, I don’t understand why `dashboard.problem.sidekiq_check` needs to be passed as an override key. The other problem checks where the translation key matches the filename don’t need that. So why is an override needed here?
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [July 24, 2026, 4:34pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/6 "2026-07-24T16:34:40Z")
> [@Moin](#):
>
> Kind of a two-in-one solution supporting both the override case and the identifier case?
Yes, correct.
> [@Moin](#):
>
> So why is an override needed here?
It isn’t needed, this likely would work fine if we did `return problem` in line 8 of sidekiq\_check.rb. They’re equivalent. (I kept the override reference to have a smaller change in that PR at the time.)
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 24, 2026, 4:55pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/7 "2026-07-24T16:55:42Z")
Is there something I can change easily on a dev install to trigger the `dashboard.problem.queue_size` error message?
I thought changing
```plaintext
def massive_queue?
Jobs.queued >= 100_000
end
```
to `>= 0` would result in that error being triggered - but this resulted in `dashboard.problem.sidekiq_check`
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [July 24, 2026, 6:06pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/8 "2026-07-24T18:06:37Z")
It’s easier to reproduce in system specs. I tried to do that and it exposed some more issues, this should fix them:
>
>
> Previously, persisted problem notices ignored custom translation keys and displa…yed incorrectly.
>
> This change stores and reuses the override when rendering admin notices.
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 24, 2026, 6:19pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/9 "2026-07-24T18:19:32Z")
> [@pmusaraj](#):
>
> It’s easier to reproduce in system specs.
For translating the Discourse interface, it’s sometimes helpful to see the text in its context, which is why I sometimes try to trigger such warnings and am always interested in learning how to do that more easily. Is that possible with system specs? Or is your “easier” only related to the context of ensuring the code works as expected?
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [July 24, 2026, 6:25pm UTC](https://meta.discourse.org/t/missing-text-dashboard-problem-sidekiq-check/395969/10 "2026-07-24T18:25:00Z")
Yes, you can use system specs to see translations in context.
If you have a dev environment for Discourse, you can do something like this:
1. add a `pause_test` statement in the system spec that you want to see in a browser
2. run that system spec in headful mode, meaning, with a full browser (by default, specs run in headless mode)
For example, for the spec above, I added `pause_test` to line 47 of `admin_notices_spec.rb` and then ran the spec with:
```plaintext
PLAYWRIGHT_HEADLESS=0 bin/rspec spec/system/admin_notices_spec.rb:47
```
That launched a browser and paused in that specific screen:
