If you can find any error logs near the times when the repeatings occurred successfully last time, please create new support ticket with details. The logs are written to the log subdirectory of your Jira application home directory (or elsewhere if you have configured a different location). File: atlassian-jira.log.
If you can't find any related errors, there could be two use cases when you can see INTERRUPTED repeatings listed on add-on administration page (Jira Administration > Issues > Repeated Issues)
- Sometimes there are some problems with cached index for Jira search service during the add-on update process. This may cause that the repeated issues are not scheduled properly after add-on update (because issues are not found). Finally, the repeated issues may have properly calculated next occurrence date but their status will be INTERRUPTED. This happen in nondeterministic way and we did changes in the add-on version from 3.1.0 to try prevent such situations.
- When the add-on is temporary uninstalled, all issues to which any change are made will be indexed without data of repeated issues. After subsequent add-on installation such situations can either lead to repeatings with INTERRUPTED status, or repeatings may be not visible at all.
Solution
Go to add-on administration page (Jira Administration > Issues > Repeated Issues) and check if you can find any repeatings with INTERRUPTED status. If present, reset all repeatings using "more" menu (...) on add-on administration page. If you suspect there are some missing repeatings, please reindex the Jira and after finish, reset all repeatings on add-on administration page.
Also, make sure, you have always the the latest add-on version.