Internal server error associated with automation rule

[Tedd Shimp]

PROBLEM: For the past 2 days I've been receiving alerts related to the failed execution of an automation rule that has been working without error for at least 2 months.

BACKGROUND: When triggered the automation rule edits the issue and adds a custom field (it adds the team based upon the assignee of the issue).

ADDITIONAL INFO: The log indicates that the rule sometimes executes correctly (see screenshot), but other times fails.

The audit log indicates that the problem is "internal server error" (see screenshot)

Any ideas as to how I can resolve this error? Is this an Atlassian support issue?

[Jim Knepley - ReleaseTEAM]

Does it only fail for specific teams, or is it seemingly random?

I assume that the assignee has a relationship to the value you're putting in the custom field. How is that relationship defined? If resolving that relationship fails or if the team name contains a character that is invalid for some reason, it could cause an error.

I've seen unexpected behaviors when external data changes, this has some of the same characteristics.

[Tedd Shimp]

Thanks for this reply. And to answer your question, yes, the assignee has a relationship to the custom field. In fact, on this particular issue, the issue has "ping ponged" a few times between assignees on different teams and the automation rule has executed successfully. This is common in my company and doesn't seem to have caused issues in the past. And, looking at the history of this particular issue, it's been assigned 2 different times to the current assignee (let's call her Jane), but on the third time the issue was assigned to her, the automation failed...

[John Funk]

Hi Tedd,

Since it is saying that it is an internal server error, your best bet would be to submit a support ticket to Atlassian and have them try to untangle it. Please post back here with the resolution. 

https://support.atlassian.com/contact/#/

[Tedd Shimp]

Thanks. I'll do that.