Custom block Token Not render

I am seeing this same behaviour with 1.1.

Amazingly, this is because block_token matches the 'last' module dependency of a block. For modules that come before block_token alphabetically (such as block_content), that means the suggested token won't work! You can however use the token browser to get a working token; which will be one using 'block_token' in place of 'block_content'. So in your case, that will be [block_token:block_token:custom].

As suggested in 🐛 Block admin page token help text provides wrong token Active , a solution could be to just remove that incorrect suggestion of the token to use. Or we put a fix in to use the 'right' token, but we'd need to preserve backwards-compatibility. To be honest, I don't think the module name really needs to be part of the token, as the ID on the end should already be unique across all blocks? So we could even just ignore the module name in any existing tokens - though as that's a behaviour change, it might warrant a new major version of the module.