Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Service schedule conflicts between xporter and scriptrunner/groovy



I've been working with scriptrunner for a while now and decided that I wanted to run one of my scripts as a service. So I setup my service following this and everything was fine until another add-on's schedule ran.

Every morning the add-on Xporter sends a report until today. Xporter  is set to run everyday at 9am and the groovy script is setup to run every hour. This morning Xporter silently died and my groovy script is now getting a nullpointerexception.

The script was running fine yesterday and it works in the script console, it's just the scheduled job that's having the issue.

When you re-create the groovy scheduled service in the GUI it works fine, it's like these schedules are sharing id's or handlers since they're running at the same time.


Any ideas on what could be causing these two schedules to fail?


Here's the stacktrace for my groovy script:

2019-03-13 09:00:07,158 Caesium-1-1 ERROR anonymous    Automated Ticketing Engine [c.o.jira.groovy.GroovyService] Script service failed: /path/to/script.groovy
	at com.atlassian.jira.issue.attachment.CreateAttachmentParamsBean$
	at com.atlassian.jira.issue.attachment.CreateAttachmentParamsBean$Builder$build$ Source)
	at org.projecthaystack.client.ticketEngine.takeScreenshot(ticketEngine.groovy:157)
	at org.projecthaystack.client.ticketEngine$takeScreenshot.callCurrent(Unknown Source)



1 answer

0 votes
Inês Silva
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 27, 2019

Hi Matt,

For similar situations, please open a ticket in our Service Desk so we can help you as soon as possible.

Our team is always happy to help!

Best regards,
Xporter Team

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events