Layouts vs. Reports

[MobiusSnake]

Hi all,

I have some map production tools which I originally built in 2013 for ArcMap 10.0, using ArcObjects and C#.  A few years ago I converted them to Python and made them work with Pro.

I'm getting ready to do a third major iteration given some updated requirements and I'm considering modifying the tools so instead of using layouts to generate PDFs, they use Pro reports instead.  I don't know much about reports though, would appreciate hearing from anyone regarding:

• Do they have any significant advantages or disadvantages versus using layouts?  The layouts currently being used involve a lot of elements like labels and tables with spatial filters based on the map extent(s).
• Have you automated their creation, and ever run into any major blockers in the process?  Specifically, have you ever hit any gaps in ArcPy where you've tried to do something and it just isn't possible?

Map series aren't part of these tools, so any differences involving those isn't important.

Thanks!

[RTPL_AU]

@MobiusSnake 
In a few cases it was easier to mimic a report by using a map series rather than trying to get Pro to behave in the Report. 
For me it was the ability to control the exact page layout and object size in a Layout vs trying to work around the edge cases without 'weird pages' in a Report.
It is a case of  "Can I get a pdf 'report' created for that one job" vs having a robust report layout for the next few years, where all data is controlled and it justifies time spent making it reliable.

I feel both approaches are useable to generate a report-like output. Best you try a creating few Reports and see if there are any hiccups created by your specific requirements.
Keep in mind that with dynamic tables, all sorts of dynamic text, and attachment inserts, over & above all the mappy things, Layouts with a map series may just give you something nicer that is less bipolar than Reports.