This forum is intended for MultCloud Support Discussion. Please post/inquire on existing discussions if they exist.
More Detail and JSON Error Reporting (and CSV maybe) #suggestion
edited December 2022 in Suggestions & Bug Reports
Hi, for those of us that utilise this for professional means, when there is a failure, it's unclear about what else has been done and not done, often the amount of files transferred will actually be more than the reported amount in the detailed view.
What would be useful would be a FULL report of what was and what wasn't transferred so that we can manually handle the issues.
I've been making some very good progress with both Power Automate, and the Google API, for example, with handling failed transfers.
I think that creating an array with error reason(s), and then a report on each file with some file metadata (a sub-object containing id, size, name, extension, original mimeType, inferred mimeType), file destination metadata (similar fields in that sub-object), copy status for each file, and top level destination metadata, and whatever else you can smoosh into it. Then you'd be giving us a fighting chance of using this to better perform business critical functions.
Generally, when the transfer fails, you can view Logs and check the failed files.
HOW TO APPROACH?