automation rule, field edit error "We couldn't save your changes. Copy your content, then try reloa"

[Bill Sheboy]

Hi community!

I have a very simple rule, with a scheduled trigger (daily) and a single custom field edit to compute Age of WIP.  This rule has run without error for 11+ months.

Yesterday it threw an error in the audit log on one issue, with no errors on the other 50+ issues processed:

We couldn't save your changes. Copy your content, then try reloading the page.

• This seems like the page timeout error seen when manually editing a page field too long
• The rule ran for just over 64 seconds, and it has run over 70 seconds successfully.  The normal run time is around 20 seconds.
• I see no indication of throttling in the performance log
• The edit completed as expected.  There were no other indications of a failure in the issue's history log.
• This is a project-scoped rule.  Other projects running project-level copies of this same rule show no errors.

Who has seen this error before?

Thanks, and best regards,

Bill

[Bill Sheboy]

Update from Atlassian support, as of 17 May 2021:

Over the last several weeks, there have been intermittent latency issues with some REST API calls, and several customers are experiencing the symptom/error we observed.  The relevant calls are:

Create an Issue
POST rest/api/2/issue

Update an Issue
PUT/rest/api/2/issue/

{issueIdOrKey}
Fetch Create metadata
GET /rest/api/2/issue/createmeta

The automation team is working on fixing these issues now.

[Yvan Martin]

Hi @Bill Sheboy,

Developer from Automation here.

That error message is coming from the underlying Jira APIs we call, but to figure out what's going on you'll need to get contact with our support channel. here: https://support.atlassian.com/contact/

Cheers.

[Bill Sheboy]

Thanks, @Yvan Martin 

I will ask our site admin to submit the request and then post back here what we learn to benefit the community.

__Bill