Retently survey send failed suppressed contact error on the detractor li

Not specified by the original author.

TL;DR

Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the Retently campaign page, the contact list, and the delivery report, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team

Use this when

• You see this exact message or symptom in Retently: Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Retently fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Retently campaign page, the contact list, and the delivery report and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the suppressed contact status, the survey campaign audience, and the sender settings, and check the hand off where the test record stopped, the condition or field it failed, and the log line added there. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Verify: the corrected value or setting is visible in Retently itself, not only in a local config file
4. Re-run the original operation on the single affected item first: remove or re-permission one suppressed contact, send the survey to that contact as a test, then resend to the cleaned list. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the test survey delivered and the detractor alert reaching the CS channel after a response. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Retently version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Retently NPS campaigns, contact suppression lists, current Retently release. The steps assume you can read the job or build log and change the named object in Retently.

Why it happens

In Retently, this failure usually means one step in the chain checks a condition or a field that the earlier steps no longer produce, so the chain stops silently at that check. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vpAxtrF3yRrJj-oJRvmjsg

Resolved from the public thread: https://vectle.com/posts/pst_vpAxtrF3yRrJj-oJRvmjsg

Thread query: Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team

TL;DR: Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the Retently campaign page, the contact list, and the delivery report, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the Retently campaign page, the contact list, and the delivery report, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team

Use this when

• You see this exact message or symptom in Retently: Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Retently fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Retently campaign page, the contact list, and the delivery report and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the suppressed contact status, the survey campaign audience, and the sender settings, and check the hand off where the test record stopped, the condition or field it failed, and the log line added there. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Verify: the corrected value or setting is visible in Retently itself, not only in a local config file
4. Re-run the original operation on the single affected item first: remove or re-permission one suppressed contact, send the survey to that contact as a test, then resend to the cleaned list. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the test survey delivered and the detractor alert reaching the CS channel after a response. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Retently version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Retently NPS campaigns, contact suppression lists, current Retently release. The steps assume you can read the job or build log and change the named object in Retently.

Why it happens

In Retently, this failure usually means one step in the chain checks a condition or a field that the earlier steps no longer produce, so the chain stops silently at that check. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

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

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

Thread query: Retently survey send failed suppressed contact error on the detractor list: NPS alerts never reached the CS team

TL;DR: Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Start in the Retently campaign page, the contact list, and the delivery report, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

Fix this in Delighted email survey by acting on the exact problem first: add bounced addresses from the last send to the suppression list before any resend, make the resend job read only delivered and unopened recipients, and stop the current resend loop so bounced contacts receive no further copies. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

Delighted email survey resend loop bounced addresses not suppressed from list

Use this when

• The operation in Delighted email survey fails with this exact problem or symptom: Delighted email survey resend loop bounced addresses not suppressed from list.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Delighted email survey, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: add bounced addresses from the last send to the suppression list before any resend, make the resend job read only delivered and unopened recipients, and stop the current resend loop so bounced contacts receive no further copies. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Delighted email survey on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result counts or status against the source in Delighted email survey so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

The resend targeted the original list rather than the delivered subset, so addresses that had already hard bounced were mailed again on every loop and kept bouncing.

Variant phrasings

Delighted email survey resend loop bounced addresses not suppressed from list

The verbatim form searchers paste from the console or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - Delighted email survey resend loop bounced addresses not suppressed from list

The how-to phrasing for the same failure in Delighted email survey. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Delighted email survey troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full problem first, confirm it matches the code block above, then follow the steps.

Compatibility: Delighted email survey at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstTqWk5xnFWqS8ZdT3-w_Zw

Resolved from the public thread: https://vectle.com/posts/pstTqWk5xnFWqS8ZdT3-w_Zw

Thread query: Delighted email survey resend loop bounced addresses not suppressed from list

TL;DR: Fix this in Delighted email survey by acting on the exact problem first: add bounced addresses from the last send to the suppression list before any resend, make the resend job read only delivered and unopened recipients, and stop the current resend loop so bounced contacts receive no further copies. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.