Better Error messaging for failed S3 rules

Related products: None

Currently when an S3 data set task fails for a reason besides the file simply not being present in the S3 bucket, we get an error that reads "Records: -1". This provides no helpful information to the customer to even begin troubleshooting their source file to see what could be missing/misconfigured.





A perfect example was a situation where a customer was trying to push a string value to a number field. With just the error that read "Message: 38, Records: -1", the customer is not offered any direction in what the root issue might be, thus leading to confusion in what to do next.





It would be helpful if we could provide better error messaging in these task failures so that customers can be more enabled to unstand potential issues with S3 data.



Tom,





Thank you for the feedback! Acknowledged!





It is great to get such feedback which helps us improve the product.





We will surely make efforts to make the experience better for you.





Thank you,





Jitin




Hi Team, 

 

Is there any progress on this idea? We are seeing lot of customers asking for this idea. 

 

Best,

Hardik


Hi Team, 

 

Is there any progress on this idea? We are seeing lot of customers asking for this idea. 

 

Best,

Hardik

@hardik_mota could you please refer this post to customers and ask them to vote here, which will increase the priority. 

 


Upvoting it, because it’s really relevant!


Just ran into this with an S3 rules as well, and all the error message in the Execution History says is Bionic Rule Execution failed: Data processing job failed while performing tasks, and as Tom pointed out, all the S3 tasks says is -1 Failed. Especially including the failure reason in the failure emails would be extremely helpful.