aikido slack notification not working on new critical finding error

Not specified by the original author.

TL;DR

Fix this in Discourse webhook to Slack by acting on the exact problem first: open the Discourse webhook delivery log, find the failed deliveries for new topic events, fix the cause shown there such as a paused webhook, a wrong event selection or a rejected payload, then create a test topic and watch it arrive in the Slack channel before declaring it restored. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

New topic notifications missing from Slack

Use this when

• The operation in Discourse webhook to Slack fails with this exact message or symptom: New topic notifications missing from Slack.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task 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 a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Discourse webhook to Slack, and copy the full message plus the post, thread, report or member 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: open the Discourse webhook delivery log, find the failed deliveries for new topic events, fix the cause shown there such as a paused webhook, a wrong event selection or a rejected payload, then create a test topic and watch it arrive in the Slack channel before declaring it restored. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, 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 Discourse webhook to Slack 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.
5. Compare the result counts or status against the source in Discourse webhook to Slack 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

Webhook failures are recorded per delivery, so the log separates a webhook that never fires from one that fires and is rejected, and each cause has a different fix.

Variant phrasings

New topic notifications missing from Slack

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

How to fix - Discourse webhook failed new topic notifications missing from Slack error failure

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

Discourse webhook to Slack 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.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: Discourse webhook to Slack at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: Discourse webhook failed new topic notifications missing from Slack error failure

TL;DR: Fix this in Discourse webhook to Slack by acting on the exact problem first: open the Discourse webhook delivery log, find the failed deliveries for new topic events, fix the cause shown there such as a paused webhook, a wrong event selection or a rejected payload, then create a test topic and watch it arrive in the Slack channel before declaring it restored. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Discourse webhook to Slack by acting on the exact problem first: restore notifications by confirming the webhook is active and subscribed to topic created events, resending a failed delivery from the webhook log to prove the receiving side accepts it, and checking the Slack app is still installed in the target channel after any workspace change. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

New topic notifications missing from Slack

Use this when

• The operation in Discourse webhook to Slack fails with this exact message or symptom: New topic notifications missing from Slack.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task 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 a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Discourse webhook to Slack, and copy the full message plus the post, thread, report or member 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: restore notifications by confirming the webhook is active and subscribed to topic created events, resending a failed delivery from the webhook log to prove the receiving side accepts it, and checking the Slack app is still installed in the target channel after any workspace change. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, 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 Discourse webhook to Slack 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.
5. Compare the result counts or status against the source in Discourse webhook to Slack 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

A removed Slack app or an uninstalled integration rejects deliveries that Discourse sends correctly, so both ends must be verified before changing the webhook configuration itself.

Variant phrasings

New topic notifications missing from Slack

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

How to fix - how to fix Discourse webhook failed new topic notifications missing from Slack fails error

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

Discourse webhook to Slack 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.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: Discourse webhook to Slack at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

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

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

Thread query: how to fix Discourse webhook failed new topic notifications missing from Slack fails error

TL;DR: Fix this in Discourse webhook to Slack by acting on the exact problem first: restore notifications by confirming the webhook is active and subscribed to topic created events, resending a failed delivery from the webhook log to prove the receiving side accepts it, and checking the Slack app is still installed in the target channel after any workspace change. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Per the Aikido workflow notes: ignore PR findings with @AikidoSec ignore: on the finding thread; a 400 means the workspace MCP ignore permission is disabled.

Steps

1. Per the Aikido workflow notes: ignore PR findings with @AikidoSec ignore: on the finding thread; a 400 means the workspace MCP ignore permission is disabled.

When to use

You are seeing this: Reply on that finding comment thread with a message starting "@AikidoSec ignore:" followed by the ignore reason. Use this skill when you run into "Ignoring an Aikido PR finding via an @AikidoSec ignore reply - and the 400 feature-disabled error".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Problem: Aikido flagged a false positive on a pull request. Reply on that finding comment thread with a message starting "@AikidoSec ignore:" followed by the ignore reason. Via the MCP server, call the ignore tool with the issue_id from the feed and the reason. If the MCP call returns "400 - Feature is disabled for this workspace", the workspace MCP ignore permission is off - point an Aikido admin at the MCP permissions settings page to enable it, and fall back to ignoring the issue manually in the UI in the meantime.

Verified resolution: Per the Aikido workflow notes: ignore PR findings with @AikidoSec ignore: on the finding thread; a 400 means the workspace MCP ignore permission is disabled.

Source URL: https://github.com/lifinance/contracts/blob/HEAD/.agents/commands/aikido-address-findings.md