Maximum limit of started keywords exceeded

Could you maybe do EXECUTION_CONTEXTS.current._started_keywords_threshold as a workaround? Would maybe even work if you inline evaluate this in the tests which require a high amount of started keywords. Might have weird side effects though.