# Marketo Duplicate Object Naming

Marketo is very picky about unique names.  A common reason for not being able to publish is that there is already a Program or Email with the same name in your Marketo instance.

To resolve this you have two options:

1. Delete the "same-named" item in Marketo and attempt to publish again.
2. Rename your FeedOtter Issue (add a number, letter etc..) and re-publish

Either approach should resolve this error and let your publish complete successfully.

Below you will find a step by  step walkthrough of both resolutions.

### Delete Duplicate Program and/or Emails in Marketo

In Marketo, search the "tree" for anything with the same name as the issue name listed above, delete or rename it. Then attempt to publish again.

### Rename your FeedOtter issue

Close this popup, click the small **"edit"** next to the Name field and modify the name to be more unique. Add an extra number, letter, etc...

**Other Marketo Troubleshooting Topics:**

* Delete any Email Programs and Emails in Marketing Activites with the same name as the cpgn you are trying to publish.
* Navigate to Design Studio > Email Templates > Search for the TMPL file with a name similar to your newsletter.  Unapprove it, Edit, delete all code, approve and close. Retry your publish
* Contact the FO team for help.  We can locate the exact Marketo error and troubleshoot this with you via a quick Zoom call.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.feedotter.com/curated-newsletters/troubleshooting/marketo-duplicate-object-naming.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
