From a risk & responsibility pov … if the scheduled post doesn’t go through & it creates a “lost opportunity” … you might be on the hook.
I know on some of the bank messaging projects I’ve worked on … this was a reoccurring concern … even with a strong TOS explicitly covering our butt
That's kind of wild, if that's the case for posting in general pretty much no one is safe for anything
sadly ... the edge cases Ive always had to account for are financial transactions based. the easy answer (IMHO) ... as long as its stated upfront that any financial losses that occur from a service disruption or other error from a missed scheduled post are bore by the account holder & not the service ... you're covered.
... my last big project was a stock trading app ... so this sort of stuff rang in my ears from the devs to the product manager. and now it's something i think about often.
Software lives on the edge, most software products you can get away with not worrying about liability, but some industries get really dicey fast. Like how the line between bitcoin nodes and custodial financial services is so thin.
