Is it worth the effort to implement new things in the task just for testing purposes? I thought of adding some kind of a flag to a request, or creating a new testing endpoint just to check if it's working, but for our case, it doesn't seem okay to have such things shipped to production. What would be alternative solutions?

Depends on subtask 1 and 2

Maybe this also depends on T374971 as we also check for actionthrottledtext in prevented errors handling, so we can't remove it until the rate-limiting subtask is done. Right?

@Ifrahkhanyaree_WMDE I was testing it via an e2e test by creating many statements (5000) as @Jakob_WMDE suggested.