> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/integrations-and-plugins/integrations/postalytics/postalytics-troubleshooting-and-error-handling.md).

# Postalytics Troubleshooting & Error Handling

{% hint style="success" %}
**Audience:** Admins, Developers, <code class="expression">space.vars.automation</code> Builders, Support & Operation teams, and Solution Architects

**Purpose:** Explains how to troubleshoot and resolve common Postalytics errors when sending mail from <code class="expression">space.vars.Kizen\_company\_name</code>.
{% endhint %}

## **Overview** <a href="#error-handling-and-troubleshooting" id="error-handling-and-troubleshooting"></a>

The table below outlines common issues you may encounter when sending Postalytics mail in <code class="expression">space.vars.Kizen\_company\_name</code>, how they appear in the UI, their likely causes, and the steps to resolve them.

| Issue                                         | How it Appears                                                                                                                                                                                                                       | Likely Cause                                                                                 | What to Do                                                                                                                                                                                                                                     |
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Send Campaign Mail action does not appear** | The Send Campaign Mail option is missing from the Perform Action menu or the <code class="expression">space.vars.automation</code> action appears but cannot be performed on the <code class="expression">space.vars.contact</code>. | Postalytics is not enabled properly                                                          | Verify the plugin is enabled, and you are on a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>. If the action is visible but unavailable, contact Support to enable the required setting. |
| **Missing required fields**                   | The send fails and lists one or more missing fields                                                                                                                                                                                  | Required <code class="expression">space.vars.contact</code> address or name fields are empty | Populate the missing fields on the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> and retry the send                                                                                     |
| **No campaigns available**                    | No campaigns appear in the campaign selection modal                                                                                                                                                                                  | No Triggered Drip campaigns exist or the API key does not have access                        | Ensure at least one Triggered Drip campaign exists in Postalytics and confirm API key permissions                                                                                                                                              |
| **Agentic Workflow step fails**               | <code class="expression">space.vars.automation</code> run is marked **Status: failed** and an email notification is sent                                                                                                             | Required data is missing, the campaign endpoint ID is invalid, or an API error occurred      | Review the <code class="expression">space.vars.automation</code> run history, correct the missing data or configuration, and rerun the <code class="expression">space.vars.automation</code>                                                   |

***

## &#x20;What's Next

Next, review [Sending Mail from a Contact Record with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-a-contact-record-with-postalytics.md) to understand required data and how to successfully send one-time mail.

You can also review [Sending Mail from Agentic Workflows with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-automations-with-postalytics.md) to learn how to include Postalytics in <code class="expression">space.vars.automations</code> and reduce manual errors.

<details>

<summary>Related Topics</summary>

* [Postalytics](/docs/integrations-and-plugins/integrations/postalytics.md)
* [Enabling Postalytics](/docs/integrations-and-plugins/integrations/postalytics/enabling-postalytics.md)
* [Sending Mail from a Contact Record with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-a-contact-record-with-postalytics.md)
* [Sending Mail from Agentic Workflows with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-automations-with-postalytics.md)

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://developer.kizen.com/docs/integrations-and-plugins/integrations/postalytics/postalytics-troubleshooting-and-error-handling.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.