> Edited your RestoreCord verification message but Discord shows the old one? Learn what Republish required means and when to use Save & publish or /setup.

Source: https://restorecord.help/verification-message-not-updating

# Verification message not updating? Republishing it the right way

You changed the verify message in Message Studio, saved it, and Discord still shows the old one. That's by design, and getting the new version live takes one click once you know which button does what.

[Open my server](https://restorecord.com/dashboard)[All setup fixes](https://restorecord.help/)

Short answer

Editing a published design never changes the post already in Discord. RestoreCord marks the slot Republish required until you publish again. Use Save & publish in the dashboard to post it and apply channel permissions, or run /setup in Discord to re-post or move it without touching permissions.

## Why the old post stays

Your verification message is a **Message Studio design** assigned to the verify slot on the server's Discord Integration card. The design and the message sitting in your channel are two different things. Saving the design updates RestoreCord's copy only, so you can work on wording without members watching every draft.

To make the gap obvious, RestoreCord flags the slot **Republish required** as soon as a published design changes. If you see that, nothing is broken. It's waiting for you.

## Three buttons, three results

| Where     | Action                | Posts to Discord          | Changes permissions        |
| --------- | --------------------- | ------------------------- | -------------------------- |
| Dashboard | Save & publish        | Yes                       | Applies your channel setup |
| Dashboard | Save without applying | No                        | No                         |
| Discord   | /setup                | Yes, re-posts or moves it | Never                      |

Pick **/setup** when you set permissions by hand and don't want anything touched. Pick **Save & publish** when RestoreCord manages your verify channel anyway. Either way the new post goes up first and the old one is deleted afterwards, so members are never left staring at an empty channel.

## When it refuses to publish

The verify slot has stricter rules than the welcome, verified, reminder and kick slots, because Discord has to be able to route the button members press.

* There must be a Verify button or a {verify\_url} link somewhere in the design. Without one, publishing is blocked.
* Only link buttons and the built-in Verify and Skip verification actions are allowed. Custom interactive buttons can't be routed from a published verify message.
* The built-in Verify action is published as a {verify\_url} link, so it works however the message was posted.

A minimal design that always passes looks like this. Variables are stored as typed and filled in when the message is sent:

Verify slot, minimal texttext

```
Welcome to {server_name}!
Verify here to unlock the server: {verify_url}
```

## Why the sender name changed

A link-only design is posted through a webhook, so your custom name and avatar show. Add **Skip verification** and the bot has to post the message itself, because webhooks can't receive button presses. Discord then shows the bot's own name and avatar. If you want the custom look back, remove that action and republish.

## Warnings from /setup

Right before it posts, `/setup` checks that the bot has View Channel, Send Messages, Embed Links and Manage Webhooks in the destination. If unverified members can't see that channel, it warns you and asks for a separate **Send anyway** confirmation.

Think twice before pressing Send anyway. A verify message nobody unverified can see means new members simply can't get in. Fix the channel's View Channel overwrite for @everyone instead.

## Test before members do

**Test Send** in the studio DMs the design to you. Custom name and avatar don't apply in DMs, so judge the content, not the sender. Then verify with a spare account in the real channel. If the AI bar stops taking requests while you iterate, you've likely hit the limit of 10 AI edits per hour; direct editing still works.

Members clicking the new button but not getting a role? See [the role order fix](https://restorecord.help/verified-role-not-given). Moved to a custom domain? Check [the redirect URL](https://restorecord.help/invalid-redirect-url) first. Everything else is on [the RestoreCord Setup Help home page](https://restorecord.help/).

## Before you republish

Four quick checks so the new message goes live the first time.

Design contains a Verify button

Or a {verify\_url} link. Without one of them the slot won't publish.

Only supported buttons

Link buttons plus the built-in Verify and Skip verification actions. Custom interactive buttons can't be routed.

Test Send looks right

The studio DMs the design to you. Remember custom name and avatar don't apply in DMs.

Pick how to publish

Save & publish when you also want permissions applied, /setup when you only want to re-post or move it.

## Verify message questions

### 

### 

### 

## Fresh message, same safety net

Republished and tested? Every member who presses that button is backed up by RestoreCord, ready to be pulled back if your server ever needs it.

[Get started free](https://restorecord.com/register)[Verify message docs](https://restorecord.com/docs/guides/create-verify-message)
