Limits and troubleshooting
Understand embed quotas and payload limits, fix saving errors, and troubleshoot cached Discord previews.
The dashboard checks your group's eligibility, your access, the number of saved embeds, and the draft's contents before publishing. Use the messages and counters in the editor to identify what needs attention.
Saved-embed quotas
The embed list shows usage for your group and for all groups currently owned by the same owner.
| Scope | Quota |
|---|---|
| One group | 30 saved embeds. |
| One group owner | 120 saved embeds across that owner's groups. |
Reaching either quota blocks creation. You can still edit existing embeds. Remove an embed to free a place, or use Open a ticket to request more in the list to contact AeroNexus support.
Payload limits
The editor displays bytes, components, and media counters. All three must stay within their limits, alongside each component's own limits.
| Counter | Limit | How it's counted |
|---|---|---|
| bytes | 3,000 | UTF-8 size of the serialized { "component": ... } payload, including JSON structure and media URLs. |
| components | 40 | The container plus its children, nested section text, section accessories, and buttons. |
| media | 10 | Total gallery items across all galleries, including each single Image. Thumbnails aren't included in this counter. |
The container holds 1–39 direct children, but nested components also count toward the overall 40-component limit. A section with one text block and one thumbnail uses three components before counting its parent container.
A gallery must contain at least one item, a button row needs at least one button, and a section needs at least one text block and one accessory. Empty text blocks and unfinished media or button URLs prevent publication.
The 3,000-byte limit isn't a character limit. Emoji and other Unicode text can use multiple bytes per character. To reduce the size, shorten text and URLs or remove components you don't need. Uploaded image contents aren't stored in the payload; their URLs are.
Resolve access and saving problems
Start with the message shown in the dashboard and use the matching action below.
| What you see | What to do |
|---|---|
| A prompt to set up Modmail | Set up Modmail and open a ticket in this group. An open or closed ticket record qualifies. |
| No Create embed button or a read-only editor | Ask your group owner for Manage Discord Embeds, including View Discord Embeds. |
| A quota message | Remove a saved embed in the affected group or owner's groups before creating another. |
| A highlighted field or a red counter | Correct the field or reduce the payload. The editor opens the affected component when you try to publish. |
| An image won't load | Use a direct PNG, JPEG, WebP, or GIF URL, or upload the image instead. Check that the host serves the image without requiring a login. |
| Invalid JSON | Check commas, quotes, and brackets, then confirm the root is component and every component uses the supported format. |
| Saving is temporarily unavailable or your connection can't be verified | Keep the editor open and try again after the service or connection recovers. The failed save doesn't discard your current draft. |
| Embed not found | Return to the group's list and confirm the embed still exists and belongs to that group. |
For image formats and component structure, see images and media and JSON import and export.
Understand delayed previews
The editor's preview follows your draft immediately. After a successful Create or Save, AeroNexus clears the public cache. This can take up to 15 seconds.
Messages you've already sent in Discord won't update. Send the link again after saving and waiting for the cache to clear to share the new version.
Confirm your changes are saved in the editor first. If the public content stays outdated, contact AeroNexus support with the embed link and a description of the expected change.
Last updated on