# Common validation issues

Validation helps prevent invalid or risky Journey configurations from being published. The publish checklist groups issues into two categories: **errors** and **warnings**.

## Errors vs warnings

| Type        | Effect                                                        | When to resolve                          |
| ----------- | ------------------------------------------------------------- | ---------------------------------------- |
| **Error**   | Blocks publishing — the Journey cannot go live until resolved | Always, before publishing                |
| **Warning** | Does not block publishing, but flags a risk or design concern | Review and consciously accept or resolve |

{% hint style="danger" %}
Do not dismiss warnings without reading them. A warning about immediate activation means real contacts will be activated without a delay. If that is unintentional, it can cause duplicate sends or an unexpected customer experience.
{% endhint %}

## Blocking errors

### Missing entry rule

**Cause:** The Start step has no valid entry rule configured.

**Fix:** Open the Start step and add at least one entry rule (Audience entry or Event occurrence).

***

### Missing destination on Activate

**Cause:** A Activate step has no destination selected.

**Fix:** Click the Activate step and configure at least one destination. Every Activate step must have at least one destination to publish.

***

### Incomplete Segment configuration

**Cause:** A Segment step is missing a field selection, has no groups defined, or has groups with no values.

**Fix:** Open the Segment step and ensure:

* A profile field is selected
* At least one group is defined
* Each group has at least one value

***

### Incomplete Pause Until configuration

**Cause:** A Pause Until step has no condition configured.

**Fix:** Open the Pause Until step and configure either a profile field condition or an event table condition.

***

### Invalid Wait configuration

**Cause:** A Wait step has no duration set, the duration is zero, or the duration exceeds the maximum (365 days).

**Fix:** Open the Wait step and set a valid duration between 1 unit and 365 days.

***

## Common warnings

### Immediate activation after Start

**What it means:** A Activate step is placed directly after Start with no Wait between them. Contacts will be activated the moment they enter the Journey.

**When to accept it:** If your business intent is to activate contacts immediately on entry (for example, a real-time welcome message), this is expected.

**When to resolve it:** If there is no deliberate reason for immediate activation, add a Wait step between Start and Activate.

***

### No timeout on Pause Until

**What it means:** A Pause Until step has no maximum duration. If the condition never occurs, contacts will wait at this step indefinitely.

**When to accept it:** Almost never. Indefinite waits create contacts that are permanently stuck at a step with no fallback.

**When to resolve it:** Set a timeout on the Pause Until step. Choose a duration that represents a reasonable business deadline (for example, 7 days, 30 days).

***

### Repeat entry without an early delay

**What it means:** Allow Journey Repeat is enabled and the first activation happens quickly after entry. Contacts who complete the Journey fast may re-enter and be reactivated faster than intended.

**When to accept it:** If re-entry with fast reactivation is a deliberate business choice.

**When to resolve it:** Add a Wait step before the first Activate to create a buffer between completion and the next reactivation.

***

## How to troubleshoot efficiently

1. **Read blocking errors first.** They must be resolved before anything else. Address them in order.
2. **Fix structural problems before design warnings.** A missing entry rule is more urgent than a timing concern.
3. **Re-review the full checklist after making fixes.** Fixing one error sometimes reveals another that was previously hidden.
4. **When accepting a warning, document why.** If the business owner agrees that immediate activation is intentional, make a note. This will help the next reviewer understand the decision.

## Related pages

* [Entry rules](/journey/concepts/entry-rules.md)
* [Pause Until](/journey/concepts/pause-until.md)
* [Wait](/journey/concepts/wait.md)
* [Designing safe Journeys](/journey/best-practices/designing-safe-journeys.md)


---

# 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.dinmo.io/journey/monitoring-and-troubleshooting/common-validation-issues.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.