Splunk HEC error "invalid token" forwarder alerts dropped during ingestion spike

Not specified by the original author.

TL;DR

Fix this in Splunk HEC by acting on the exact message first: replace the forwarder HEC credential with the current indexer credential value, restart the forwarder, send one test event, and confirm it is searchable in Splunk before declaring the ingestion spike recovered, then check the dropped window for events that need replaying. 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.

Splunk HEC error "invalid token" forwarder alerts dropped during ingestion spike

Use this when

• The operation in Splunk HEC fails with this exact message: Splunk HEC error "invalid token" forwarder alerts dropped during ingestion spike.
• The same failure repeats on retry with unchanged inputs.
• An alert, incident or enrichment step is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error 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 Splunk HEC, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: replace the forwarder HEC credential with the current indexer credential value, restart the forwarder, send one test event, and confirm it is searchable in Splunk before declaring the ingestion spike recovered, then check the dropped window for events that need replaying. Verify: the single failing item now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check the neighbouring items that share the same config, template, feed 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 alerts against the source in Splunk HEC 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 in Splunk HEC on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message 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 error, the fix applied and the evidence of success.

Why it happens

Splunk rejects every event from a forwarder whose HEC credential no longer matches the indexer configuration, and the forwarder queues or drops those events while the spike hides the rejection in volume.

Variant phrasings

Splunk HEC error "invalid token" forwarder alerts dropped during ingestion spike

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

How to fix - Splunk HEC error "invalid token" forwarder alerts dropped during ingestion spike

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

Splunk HEC troubleshooting for this failure

The symptom-first 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: Splunk HEC at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/psti0lZb5WJwqs-p02Gc4G-g

Resolved from the public thread: https://vectle.com/posts/psti0lZb5WJwqs-p02Gc4G-g

Thread query: Splunk HEC error "invalid token" forwarder alerts dropped during ingestion spike

TL;DR: Fix this in Splunk HEC by acting on the exact message first: replace the forwarder HEC credential with the current indexer credential value, restart the forwarder, send one test event, and confirm it is searchable in Splunk before declaring the ingestion spike recovered, then check the dropped window for events that need replaying. 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.