There are a few places where an exception might occur in the import process, including if authentication or authorization fails. In these instances, no dblog message is generated. This is obviously bad considering that most imports probably occur on cron, so the exceptions won't be visible to the user.

Instead of addressing every instance of this, it might be better to see if Feeds can fix it in core somehow.

Comments

danepowell’s picture

danepowell commented

There is also some discussion of error handling at #1411844: Failed authentication breaks imports

danepowell’s picture

danepowell commented

Here's how I want to attack this issue: first enumerate and categorize all possible message/error sources within the import process (Mailhandler Fetcher, Mailhandler Parser + plugins, Feeds Node Processor). Then figure out what makes the most sense for configuration options - do people want to get notified based on severity, or based on event source (i.e. authentication failure)?

Finally, post a feature request in Feeds queue with this solution, and in the meantime implement a workaround in Mailhandler.

danepowell’s picture

danepowell commented
Status: Active » Postponed

Waiting on #1562030: Unified error-handling function

danepowell’s picture

danepowell commented
Status: Postponed » Active
danepowell’s picture

danepowell commented
Issue summary: View changes
Status: Active » Closed (won't fix)