Skip to content

Docs: Personalization failed badge for multi-location posts (SM-4194)#818

Draft
haleyserrano wants to merge 1 commit into
masterfrom
claude/practical-heisenberg-xzkw9j
Draft

Docs: Personalization failed badge for multi-location posts (SM-4194)#818
haleyserrano wants to merge 1 commit into
masterfrom
claude/practical-heisenberg-xzkw9j

Conversation

@haleyserrano

@haleyserrano haleyserrano commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

JIRA

SM-4194 — Localization - Personalization failed and Tooltip

Classification

UI/UX change — new error state (badge + tooltip) for multi-location social posts.

Repo targeted

Partner Center (multi-location workflow documentation)

Summary of updates

Updated the existing Manage Posts in Multi-Location Social article (docusaurus/docs/multi-location-business-app/social/manage-posts-social-multi-location.mdx):

  • Added a bullet under "Viewing posts across all locations" documenting the Personalization failed badge that replaces the standard per-location error message when content personalization fails for one or more locations, including the exact tooltip copy.
  • Added a new FAQ entry clarifying that, unlike other failed posts, these can't be edited or reattempted — the post must be deleted and recreated.

Existing docs updated vs. new docs created

Updated existing documentation. No new page was created — the article already documents the "Failed" tab and per-location error surfacing for multi-location posts, so this new failure mode fits directly alongside it.

Placement reasoning

This is the Partner Center article that already covers multi-location post statuses (Drafts/Scheduled/Published/Failed) and per-location error detail, making it the natural home for this new failure state rather than a new page.

Acceptance criteria coverage

  1. "Personalization failed" badge displayed on the post — documented.
  2. Tooltip text on hover — documented verbatim.
  3. Applicable to web and mobile — documented.
  4. Applicable to multi-location only — documented (this doc is scoped entirely to multi-location).

Figma / images

None provided directly on the ticket usable here (two Jira attachments show the production UI, but they aren't accessible as image assets for this repo). Documentation is text-based per the acceptance criteria and confirmed via ticket comments describing the production behavior.

Skills used

None of the repo's specific skills applied; changes were validated manually against this repo's CLAUDE.md markdown rules (no > blockquote characters, closed <details>/<summary> tags, valid frontmatter).

Assumptions / limitations

  • The parent epic (SM-1337, "UX Improvements — Social Marketing & Business App Social") is not marked Done and is a large, ongoing umbrella epic (~95 linked tickets spanning many unrelated features). No sibling tickets under it show feature-flag/eligibility/rollout-gating signals for this specific personalization-failure badge. The story itself is Done, and ticket comments from the developer confirm the change is live in production ("The changes has been moved to production...").
  • Per the linked PR (vendasta/galaxy#33519), edit/schedule actions are hidden for posts in this failed state — only delete-and-recreate is supported. Called out explicitly since the existing "Can I fix failed posts?" FAQ (for generic failures) says edit/reattempt is possible — this new FAQ entry distinguishes the personalization-failure case.
  • No screenshot was added since the Jira attachments weren't accessible as image files for this repo.

cc @ahnikakuse @haleyserrano @maryam6samadi


Generated by Claude Code

…posts (SM-4194)

Multi-location posts that fail to personalize content for one or more
locations now display a "Personalization failed" badge with a tooltip
instead of a standard per-location error, and must be deleted and
recreated rather than edited or reattempted.
@haleyserrano
haleyserrano requested a review from ar-av-i July 24, 2026 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants