loopio reviewer assignment stuck in pending

loopio reviewer assignment stuck in pending: how to fix it

A Loopio reviewer assignment stuck in pending usually means the reviewer never got the notification, or they opened it and the accept click didnt register. Nudge them directly, and if they confirm they accepted, remove and re-add the assignment. The task almost always unsticks on the second assignment.

loopio reviewer assignment stuck in pending

When to use this skill

• A review task sits in pending past its due date
• The reviewer says they accepted but the status never changed

When not to use this skill

• Nobody was ever assigned (assign someone first)
• The reviewer declined (that is a completed decision, not a stuck task)

Tool compatibility

Loopio cloud. Review workflow task assignments. 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 review task sits in pending past its due date, start at step 1 below.
• If instead nobody was ever assigned (assign someone first), 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 whether they were notified

Ask the reviewer if they got the assignment email or in-app notification.

Expected: they say no, which points at notification delivery, or yes, which points at the accept action.

2. Resend the notification

In the task list, use the remind or resend option on the pending assignment.

Expected: the reviewer confirms receipt this time.

3. Remove and re-add the assignment

Delete the pending assignment and create it fresh for the same reviewer.

Expected: the new assignment moves to accepted or in progress normally.

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 whether they were notified): Expected: they say no, which points at notification delivery, or yes, which points at the accept action.
• Step 2 (resend the notification): Expected: the reviewer confirms receipt this time.
• Step 3 (remove and re-add the assignment): Expected: the new assignment moves to accepted or in progress normally.

Quick recap

1. Check whether they were notified
2. Resend the notification
3. Remove and re-add the assignment

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

loopio review task pending forever

Usually a missed notification, the resend fixes most of them. If this matches what you saw, the steps above apply as written.

reviewer assignment not updating loopio

The accept click sometimes fails silently, re-adding the task clears it. If this matches what you saw, the steps above apply as written.

Why it happens

The pending state waits on two separate events, notification delivery and the reviewer accept action. If either one fails silently, the task sits in pending with no error and no retry.

Edge cases

• Reviewers with full inboxes miss the notification, a direct message works better
• Re-adding loses the original assignment timestamp
• Bulk reassignments during workflow changes can orphan pending tasks

Provenance

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