A rule shows This rule has failed runs when its action failed for at least one post in the last 30 days. Your keywords still match posts. The rule found the post, but the next step, such as adding it to a collection or sending it to Slack, did not finish.
Does the rule still work?
Yes, in most cases. A failed run is about one post at one time. The rule keeps checking new posts and acts on the next match. Feeder pauses a rule only when it can't go on, for example when a Microsoft Teams channel is gone or a Telegram group changed. A paused rule shows a Resume button and the reason it stopped.
How do I see what failed?
- Select Rules in the left sidebar.
- Select This rule has failed runs next to the rule. Or open the rule and select Open error log.
- The log lists up to 20 failures from the last 30 days, each with a message and a date.
What do the messages mean?
| Message | What it means | What to do |
|---|---|---|
| Could not add post to collection. An internal error occurred. | A problem on Feeder's side stopped that post from being saved to the collection. | Nothing, if it happened once or for a short time. The rule keeps adding new posts. To get the missed posts back, see below. |
| Slack said an error happened on their end, or Microsoft, Discord or Telegram is returning an error | The other app didn't accept the post at that moment. | Nothing, if it is rare. If it happens often, e-mail us. |
| Slack connection broke, or No valid login for Slack found | Feeder can no longer post to your Slack workspace, often because the Feeder app was removed from it. | Open the rule and connect Slack again. See Automatically post news to Slack. |
| The Feeder bot needs to be added to the channel or conversation to be able to post. | The Feeder bot isn't in that Microsoft Teams channel. | Add the Feeder bot to the channel. |
| The server responded with an error status code: 404. Retry #1 | Your webhook address answered with an error. Feeder tries the same post again up to 8 times, and waits longer each time. 404 means the address wasn't found, and 500 means your app had an error. | Check the address in the rule and that your app is running. See webhooks. |
| No selected target collection, or No channel selected | The rule is missing a setting. | Open the rule, pick the collection or channel, and select Save rule. |
How do I get back the posts that were missed?
A rule doesn't go back for posts it missed. For an Add to collection rule, you have two options:
- Add them by hand. Find the post in its feed and select Add to collections. This keeps everything already in the collection.
- Rerun the collection's rules. In Library, Collections, select the collection, then Rerun under Rules. Rerun empties the collection first, including posts you added by hand. Then it runs every rule for that collection on the latest 500 posts in each feed.
Rules that send posts to Slack, Microsoft Teams, Discord, Telegram or a webhook can't send a missed post again.
When does the warning go away?
By itself, 30 days after the last failure, if no new one happens. You can't clear it by hand.
Still stuck? E-mail support@feeder.co with the rule's name and the message from the error log, and we'll help.