Thanks for getting in touch! That does look like the correct issue. It looks like we resolved this in Octopus version 2018.8.6, the next patch version up from the version you have reported using. It would be a good idea to upgrade your Octopus version and see if that resolves this issue.
If the upgrade does not resolve the issue, you will need to run the SQL query.
Let me know how you go here. If you have any questions or run into any issues with this, please do not hesitate to let me know.