> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/superoffice/integration-queue-failed-automations.md). # Why did the SuperOffice automation fail? The known reasons a SuperOffice automation event fails, and how to resolve each one before re-enqueuing it in the Integration Queue. Failed SuperOffice automation events are listed in the Integration Queue at (login required). From there you can review failed events and re-enqueue them to retry. Below are the known reasons a SuperOffice automation event fails, along with the suggested resolution for each. ## Missing mandatory information If the contact is missing mandatory contact information, the automation fails and a yellow warning triangle is shown. The mandatory fields are: * Email * First name * Last name * Company (only applicable in older SuperOffice installations) Add the missing information to the contact, then re-enqueue. ## Bad External ID When a contact triggers a SuperOffice automation, eMarketeer checks the contact's External ID field. If the field has a value, eMarketeer attempts the SuperOffice task using that value as the SuperOffice contact id. If no SuperOffice contact matches the value, the automation fails. Import the contact from SuperOffice again. The import matches on email address and saves the correct Contact ID as the External ID. Then re-enqueue. See [How contacts are matched between eMarketeer and SuperOffice](/integrations/superoffice/superoffice-contact-matching.md). ## Automation refers to old SuperOffice resources Older automations may reference SuperOffice resources that have since been deleted, such as projects, selections, or interest codes. If the referenced resource no longer exists, the automation fails. Edit the automation to reference existing SuperOffice resources, then re-enqueue. ## No connection to server or throttled network If you use your own SuperOffice server and the server is down, the network is down, or anything else prevents eMarketeer from communicating with the server, the automation fails. When a large volume of automations or feed activities is generated, the SuperOffice server may also throttle communication and prevent the task from running. Wait until SuperOffice can be reached, then re-enqueue. ## SuperOffice Online service overloaded On rare occasions, SuperOffice Online is under heavy load and the service is disrupted. Automations fail while the service is unreachable. Wait until SuperOffice can be reached, then re-enqueue. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.emarketeer.com/integrations/superoffice/integration-queue-failed-automations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.