Community
Select to view content in your preferred language

Report Generation Temporarily Down

210
3
3 weeks ago
abureaux
by MVP Frequent Contributor
MVP Frequent Contributor
3 weeks ago

This just started in the last 5 minutes for me. The issue being that reports are timing out with esriJobSubmitted.

Looks like it may have already fixed itself (as per below image). Just posting this here in case others run into the same issue today.

abureaux_0-1763404263412.png

EDIT: Looks like this issue is still on-going. It seems that some reports are squeezing through. This is similar to an issue earlier in the year, so if I had to guess, I'd say there is a resourcing issue (e.g., there are an abnormal number of submissions right now).

 

0 Kudos
3 Replies
OrrinFeril
by
Occasional Contributor
3 weeks ago

Similar issue found yesterday. It might be related.

Post

0 Kudos
ZhifangWang
by Esri Regular Contributor
Esri Regular Contributor
2 weeks ago

Hi @abureaux ,

Thanks for the feedback and sharing the screenshot. It indicates that the printing request was accepted by the report service, but it did not proceed to the subsequent steps (e.g. prepare, print, etc.).

Could you please let us know how frequently you observe this issue? Does it occur with a specific report template and data? If the jobs shown in the screenshot ultimately failed, sharing the job IDs with us would help with our investigation.

0 Kudos
abureaux
by MVP Frequent Contributor
MVP Frequent Contributor
2 weeks ago

This issue persisted for ~3 hours (on and off). 

Here are a couple Job Ids, both of which timed out with esriJobExecuting:

  • 4d1e561585854707976ab4761daeb6a0
  • 6396d5a035fd4c2f90ede1ef5e9dfdbd

Earlier in the year, this issue was very frequent and was the topic of a support case I had opened to track down the issue. As the issue was transient, troubleshooting was difficult. But after a few months, we were able to track the issue down to resourcing on Esri's end. Since then, and with the addition of additional server resources, this issue has only popped up twice (that I can remember, at least). This time was more significant than the previous.

I have a pretty consistent stream of reports being generated daily, and get notified if there is an issue with any of the flows. As a result, I tend to see more small outages more often. Since I can't really differentiate between a full service outage (e.g., an bad AGO update that leaves me without service for a full day) and something like this (i.e., a transient blip), I tend to be risk adverse and assume the worst after ~15 minutes of consistent fails.

tl;dr, I'll be keeping an eye out for similar outages.

0 Kudos