In reply to Nick Diego.

As our authors do not have access to cache settings, this is not an option. Obviously there is no solution at this point, besides disabling caching on a more general level, which voids the purpose but on the other hand is also not your plugins fault.

Probably there should be general flags for blocks or an API in core, which content can be cached and which can't or how soon it should expire.