# pandadoc document stuck in sent status: how to fix it

A PandaDoc document stuck in sent status usually means the recipient never opened it, or the open wasnt tracked. Check the activity feed to see if there was any engagement, then nudge the recipient with a fresh link. If they swear they signed, check whether they signed a duplicate instead.

```text
pandadoc document stuck in sent status
```

## When to use this skill
- A document sits in sent with no movement
- The recipient claims they never got it

## When not to use this skill
- The status is draft (it was never sent)
- The recipient declined (a completed decision)

## Tool compatibility
PandaDoc document status and activity tracking.
Related area: business SaaS platforms and vendor portals.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with a document sits in sent with no movement, start at step 1 below.
- If instead the status is draft (it was never sent), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Check the activity feed

```
Open the document and review the activity timeline for opens or partial progress.
```
Expected: either no activity (they never opened it) or a stalled partial session.

### 2. Nudge with a fresh link

```
Send the recipient a new signing link and confirm they can open it.
```
Expected: they confirm receipt and open the document.

### 3. Check for duplicates

```
Search your documents for a second copy the recipient might have signed instead.
```
Expected: either no duplicate or a completed twin you can use.

### 4. Set a reminder cadence

```
Turn on automatic reminders for the document.
```
Expected: the system nudges them until they act.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (check the activity feed): Expected: either no activity (they never opened it) or a stalled partial session.
- Step 2 (nudge with a fresh link): Expected: they confirm receipt and open the document.
- Step 3 (check for duplicates): Expected: either no duplicate or a completed twin you can use.
- Step 4 (set a reminder cadence): Expected: the system nudges them until they act.

## Quick recap
1. Check the activity feed
2. Nudge with a fresh link
3. Check for duplicates
4. Set a reminder cadence

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### pandadoc stuck on sent
No activity means they never opened it, nudge them. If this matches what you saw, the steps above apply as written.

### document not moving pandadoc
Check for a signed duplicate before resending. If this matches what you saw, the steps above apply as written.

## Why it happens
Sent is a waiting state with no timeout. If the email went to spam or the recipient opened a stale link, the document waits forever with no error, looking stuck when it is really just ignored.

## Edge cases
- Spam filters eat PandaDoc emails regularly, ask recipients to check
- Automatic reminders only work if enabled per document
- A recipient who forwards the link can break tracking

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_U7zMnAJfCSSDLXxSxtoOaA