AlertCentral trashes alerts only if there is a source rule that explicitly specify to do this in some user defined situations (AC does not have this policy by default).
If you have no rules or incoming email does not match any of the existing rules than new alert will be created (but in 'Triggered' state; not assigned to any group or user).
I don't know why in your case behavior is different.
Can you attach logs, so we can try to look closer at this problem? (Instructions for collecting Alert Central Logs)
I have yet to impliment the Alert Central; But I was able to find a report that shows you the alerts and actions when they are triggered.
** Sorry to the developer for lack of reference, msg me and I can edit this, I could not find the post that this came from.
It will show you if the initial email out of NPM Alerts has failed for any reason, and this has helped me to fix several alert issues.
SELECT TOP 1000 *
where ActionType = 'EMail'
order by LogDateTime desc
I figured out where the problem is: the "lost mails" did have an empty body, which is fine for the thing which they should do. If I add some fooBar text to the body they arrive in AlertCentral.
So there must be something wrong with your email parser, add a testcase for this and fix the problem, PLEASE!
Yes you right here, in previous version we have problems with mail that does not contains text.
Also you can have this behavior if you forward (FW) or reply (RE) mails to AlertCentral (we try to process them as user response).
Both issues are fixed right now and will be available soon in next release.
Is there any list of known bugs? Just in case there is some more which you already know to go wrong.
And maybe a mailing list or RSS regarding bugs would be awesome to get an idea what to check if you want to use this software in production.
That is for the Orion Report Writer; and should display on the web without issues, i run 10.5 currently. Reference the Message section for details.