Jira background re-index failed - error in scriptrunner field

[Andrey Vorobets]

Jira background re-index failed errors like
2018-04-15 15:11:41,040 JiraTaskExectionThread-118 WARN voro005 1218x10177292x1 7y0qcr 162.49.176.15 /secure/admin/IndexReIndex.jspa [atlassian.jira.index.AccumulatingResultBuilder] Indexing failed for Issue - '42407'
2018-04-15 15:11:41,040 JiraTaskExectionThread-118 WARN voro005 1218x10177292x1 7y0qcr 162.49.176.15 /secure/admin/IndexReIndex.jspa [atlassian.jira.index.AccumulatingResultBuilder] java.lang.Exception: This issue is not associated with this field - check the custom field context
java.lang.RuntimeException: java.lang.Exception: This issue is not associated with this field - check the custom field context
at com.atlassian.jira.index.DefaultIndex$Failure.<init>(DefaultIndex.java:123)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$2.perform(DefaultIssueIndexer.java:217)
-------------
Caused by: java.lang.Exception: This issue is not associated with this field - check the custom field context
at sun.reflect.GeneratedConstructorAccessor1778.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:247)
at com.onresolve.scriptrunner.customfield.GroovyCustomField.getRelevantConfig(GroovyCustomField.groovy:315)
at com.onresolve.scriptrunner.customfield.GroovyCustomField$getRelevantConfig$0.callCurrent(Unknown Source)
at com.onresolve.scriptrunner.customfield.GroovyCustomField.getValueFromIssue(GroovyCustomField.groovy:163)
at com.atlassian.jira.issue.fields.CustomFieldImpl.getValue(CustomFieldImpl.java:454)
at com.atlassian.jira.issue.index.indexers.impl.SortableTextCustomFieldIndexer.addDocumentFields(SortableTextCustomFieldIndexer.java:44)
at com.atlassian.jira.issue.index.indexers.impl.SortableTextCustomFieldIndexer.addDocumentFieldsNotSearchable(SortableTextCustomFieldIndexer.java:38)
at com.atlassian.jira.issue.index.indexers.impl.AbstractCustomFieldIndexer.addIndex(AbstractCustomFieldIndexer.java:50)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.add(DefaultIssueDocumentFactory.java:102)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.addAll(DefaultIssueDocumentFactory.java:91)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.apply(DefaultIssueDocumentFactory.java:60)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.apply(DefaultIssueDocumentFactory.java:37)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$DefaultDocumentCreationStrategy.get(DefaultIssueIndexer.java:644)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$2.perform(DefaultIssueIndexer.java:182)
-------------------------------------------------------

And as result re-index was failed
How we can identify a problem field ?
We have ~100 script runner fields
I checked some issues from the log and don't see associated customfield / customfieldvalue rows with the scriptrunner fields in those issues

[Jeffrey Melies]

@Andrey Vorobets, Did you find a solution for this?