Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Scriptrunner errors after upgrading to 4.* version

Hi There,


We've updated to the latest available version of Scriptrunner for our 6.4.7 JIRA version and now I see errors in the log file:

2018-02-01 09:50:01,372 atlassian-scheduler-quartz1.clustered_Worker-1 ERROR automation [atlassian.scheduler.core.JobLauncher] Scheduled job with ID 'com.onresolve.jira.groovy.groovyrunner:EscalationService-job:-266997063' failed
groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[interface com.atlassian.crowd.embedded.api.User]
[interface com.atlassian.jira.user.ApplicationUser]
at groovy.lang.MetaClassImpl.chooseMostSpecificParams(
at groovy.lang.MetaClassImpl.chooseMethodInternal(
at groovy.lang.MetaClassImpl.chooseMethod(
at groovy.lang.MetaClassImpl.getMethodWithCachingInternal(
at groovy.lang.MetaClassImpl.createPojoCallSite(
at org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(
at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.runService(EscalationService.groovy:406) <+2> (
at java.lang.reflect.Method.invoke(
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.execute(EscalationService.groovy:334)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService$execute$0.callCurrent(Unknown Source)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.runJob(EscalationService.groovy:432)
at com.atlassian.scheduler.core.JobLauncher.runJob(
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(
at com.atlassian.scheduler.core.JobLauncher.launch(
at com.atlassian.scheduler.quartz1.Quartz1Job.execute(
at org.quartz.simpl.SimpleThreadPool$

I can't understand where they are coming from. 

Any help is appreciated, thanks. 


4 answers

1 vote

I seem to remember this cropping up a while ago, internally.  Try raising it with the SR team at

Appears to be from EscalationServices settings. Increased interval stopped errors from appearing in log file. However manual running does not produce any errors. 

Anyone? Any ideas? 

In Installed plugins there is only one version of scriptrunner:

ls installed-plugins/ | grep -i groo

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Partner Webinar Opportunities: January 2022

Hi everyone 👋, I really like the format of the webinar opportunities summary that @Jimmy Seddon posts monthly on the Welcome Centre group. It's a great place to go to check that you didn...

134 views 3 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you