gwtoolset does log batch uploads to the runJobs.log and any issues it runs into during that upload are recorded there. i was able to access that log on beta, but on production, i have no idea. hashar recommended that we create a separate gwtoolset log, and i agree that we should, but that still wouldn't help an end user. when we started development, echo, http://www.mediawiki.org/wiki/Echo_(Notifications), wasn't available, so we decided not to spam a user’s talk page with updates from gwtoolset. now that echo is available, it makes sense to create some notification system with it. by happenstance, bawolff created this bug today https://bugzilla.wikimedia.org/show_bug.cgi?id=67144 that makes this request. fae’s tips below are good. i would add that they should first be tried out on beta before attempting to run the batch on production. if the batch worked on beta, and not commons, then my concern is that something in the production environment may be creating the issue. in either case, it would be good to see the xml file and metadata mapping Nicolas was using so that i can test it out in my dev environment and see if i can spot the issue. might be best to create a ticket, attach the xml file to it and a link to the metatdata mapping he was using. with kind regards, dan On Jun 26, 2014, at 19:08 , Fæ <faewik(a)gmail.com> wrote: