ENTITY_IS_DELETED: entity is deleted salesforce error

Not specified by the original author.

TL;DR

The record was deleted (or is in the recycle bin), so the update fails. Query with ALL ROWS to confirm, undelete it if needed, or point the operation at the surviving record.

Error

ENTITY_IS_DELETED: entity is deleted

Steps

1. Re-run the query with ALL ROWS to see the deleted record Expected: you confirm it is deleted, not missing.
2. Undelete it from the recycle bin if the delete was a mistake Expected: the record is back.
3. Or update your code to skip deleted records Expected: the operation targets live records.
4. Re-run the original operation Expected: it succeeds.

When to use

• ENTITYISDELETED on update or delete
• The record was deleted

When not to use

• The record never existed (then check the ID)
• You want it deleted (then the error is harmless)

Tool compatibility

• Salesforce recycle bin and ALL ROWS
• Data loader and API upserts

Variant phrasings

entity is deleted salesforce

The record is in the recycle bin. Undelete it or skip deleted rows.

ENTITYISDELETED

Same: query ALL ROWS to confirm, then undelete or retarget.

Why it happens

Agents cache record IDs from earlier in the run. Another process (or an earlier step) deletes the record, and the cached ID goes stale.

Edge cases

• Records purged from the recycle bin cannot be undeleted
• Hard-deleted records need re-creation, not undelete

Provenance

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

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

Thread query: "ENTITYISDELETED: entity is deleted" salesforce error

TL;DR: The record was deleted (or is in the recycle bin), so the update fails. Query with ALL ROWS to confirm, undelete it if needed, or point the operation at the surviving record.

Not specified by the original author.

TL;DR

Fix this in deletion propagation to search by doing this first: delete the subject documents from the search index and purge the cached copies, force an index refresh, and verify by searching for the erased profile identifiers and getting no results. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

search index still returns erased profile

Use this when

• The operation fails with this exact problem: search index still returns erased profile.
• The same failure repeats on retry with unchanged inputs.
• An audit, review, or request is blocked until this item completes.

Not for this skill when

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

Steps

1. Reproduce the failure with the smallest scope that still shows it in deletion propagation to search, and copy the full message plus the item, account, or request involved into the run notes. Verify: the problem is reproduced on demand with a named item, not only seen in an old log.
2. Apply the specific fix for this problem: delete the subject documents from the search index and purge the cached copies, force an index refresh, and verify by searching for the erased profile identifiers and getting no results. Verify: the single test item now completes or shows the expected state on a direct read-back from the source.
3. Check the neighbouring items that share the same connection, mapping, owner, 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. Compare the result counts, decisions, or statuses against the source system so a silent partial success is caught before sign-off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation 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.
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

Deletion removed the source record but the index and its cache keep serving the indexed copy until an explicit removal or refresh, so the erased profile stays publicly findable.

Variant phrasings

deletion propagation error search index still returns erased profile failure cache

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

How to fix this failure in practice

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

Troubleshooting the symptom-first form

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

Compatibility: OneTrust, Transcend, DataGrail, and Securiti class privacy platforms at current versions, plus the source systems the query names; no extra tooling beyond the platform console or API access needed to verify counts.

Provenance

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

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

Thread query: deletion propagation error search index still returns erased profile failure cache

TL;DR: Fix this in deletion propagation to search by doing this first: delete the subject documents from the search index and purge the cached copies, force an index refresh, and verify by searching for the erased profile identifiers and getting no results. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

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 Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout, 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.

Gainsight rule action failed object mapping error on success plan creation: overdue objective task never assigned

Use this when

• You see this exact message or symptom in Gainsight: Gainsight rule action failed object mapping error on success plan creation: overdue objective task never assigned
• 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

• Gainsight 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 Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout 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 rule action field mapping, the scorecard measure config, the source object fields, and the 360 page sections, 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 Gainsight itself, not only in a local config file
4. Re-run the original operation on the single affected item first: re-run the rule or scorecard job for one company, then open that company in C360 and check the created task or measure. 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 success plan objective task assigned to the owner and the scorecard measure showing a value instead of a blank. 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

Gainsight rule action failed object mapping error on success plan creation: overdue objective task never assigned

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

Gainsight 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 gainsight rule action failed object mapping error on success plan creation: overdue objective task never assigned 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: Gainsight NXT Rules Engine and Scorecards 2.0, Salesforce or Snowflake data sources, C360 layouts. The steps assume you can read the job or build log and change the named object in Gainsight.

Why it happens

In Gainsight, 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_ZOc-HhE4mtdj-w82jnnTQw

Resolved from the public thread: https://vectle.com/posts/pst_ZOc-HhE4mtdj-w82jnnTQw

Thread query: Gainsight rule action failed object mapping error on success plan creation: overdue objective task never assigned

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 Gainsight NXT administration pages, the Rules Engine execution log, and the C360 layout, 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.