Forums - Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 320 subscribers
  • Views 622 views
  • Users 0 members are here
Forum Actions
Related

Scheduled report too big

Francesca Shiekh

I suspect that I have some reports scheduled by users that result in files too big to send via email.

I am seeing errors like the following in my logs:

Wed May 13 18:05:09 2020 [20239][2488a848-2e7a-4290-87c0-4d2b6c6408e4][FATAL] PHPMailerProxy encountered an error: SMTP Error: data not accepted.SMTP server error: DATA END command failed Detail: Error: message file too big SMTP code: 552 Additional SMTP info: 5.3.4

I know that the id of the user is in the message in the square brackets before [FATAL] but
what is the best way to figure out which one, out of the many reports scheduled by that user this one is?

thanks,

FrancescaS

Parents
  • 0

    Francesca,

    I would increase the logging level from FATAL to INFO and then attempt to capture the failure again.  The information surrounding the FATAL should include the report ID that ran.  If this is in an instance hosted by us then I recommend filing a case with Support to assist with determining the specific report(s) causing failures since you cannot modify the logging level.  Another option would be to run each report scheduled by this user and focus on the largest ones that are generated.

Reply
  • 0

    Francesca,

    I would increase the logging level from FATAL to INFO and then attempt to capture the failure again.  The information surrounding the FATAL should include the report ID that ran.  If this is in an instance hosted by us then I recommend filing a case with Support to assist with determining the specific report(s) causing failures since you cannot modify the logging level.  Another option would be to run each report scheduled by this user and focus on the largest ones that are generated.

Children
No Data