Long names and pasted text no longer make a save fail

What this solves

• A name made from a longer one could be too long to save. Examples: a task template named after its task, a people list named after its company list, a sources title taken from a file name.
• Pasting a long question, page title, tag, link, change request or edited message let you type past what could be saved. The save then failed with a generic "Something went wrong".
• A post in bulk posting could gather more than 24 picture options and stop saving.
• Assigning more than 500 companies to a rep at once, or pausing more than 20 ads from a Next move, failed as a whole.
• Hashtag rules that grew past 280 characters once each tag got its "#" failed without saying why.

What changed

• Every field with a limit stops at it while you type or paste.
• Names made from a longer name are cut at a word and end in "…".
• Bulk posting keeps the newest 24 options and the first 10 files of a post.
• Large rep assignments and ad pauses are sent in parts, so they all go through.
• Hashtag rules say when they are too long before you save.
• Humanise in Grow is off for replies too short to rewrite, and its errors now say why it failed.
• Automatic error reports are no longer lost when the error text is very long.

Where to find it

Everywhere you name, paste or edit text: Sales (lists, campaigns, drafts, Send back), Campaigns (UTM links, Request changes, uploads), Creatives (tags, saved ideas, size changes), Calendar (bulk posting, copy rules), Tasks (templates) and Website (AI visibility questions and content ideas).

Useful for

• Teams whose list and campaign names are long and descriptive.
• Anyone who pastes long text into a field.
• Admins who assign hundreds of companies to reps at once.