We identified that the problem affected only a few misconfigured Jira instances. Due to changes in permission schemes Clockwork was disallowed to read issues. Fixing the permission scheme solved the problem.
Posted Jun 09, 2021 - 09:20 BST
We found out that only a few instances are currently affected. It seems it's most likely a misconfiguration in Jira than a bug in our application. But we're still gathering more information.