If possible, redesigns preceded by targeted warning emails sent to business customers based on message length stats, with a timetable for when the fix will rollout.
If that data doesn’t exist, public announcement that the API is breaking long messages without the new parameter.
If the API can’t be broken, version the API and break it in the new one and for new customers.
In all cases, disclosure in the documentation - If you know there’s a limit and you still exceed it, at that point, as the kids say, FAFO.
If that data doesn’t exist, public announcement that the API is breaking long messages without the new parameter.
If the API can’t be broken, version the API and break it in the new one and for new customers.
In all cases, disclosure in the documentation - If you know there’s a limit and you still exceed it, at that point, as the kids say, FAFO.