Closed OmgImAlexis closed 2 years ago
This is normal! Can't run rules that depend on user history if the user history isn't available. The exception is caught (and logged) -- running checks for the activity just ends early since we can't be sure if this check would trigger or not because of the lack of history.
I could prevent it from printing a stacktrace if its confusing whether this is handled or not.
Newer versions of CM now include "blameable" stack traces which show "caused by" traces so, while this will still produce a stack trace, it should be easier to understand what happened and why it happened. Also, it should still be an error since the event/rule didn't run due to the history 404 being "unexpected", IMO.
going to close this for now, if you think I should change the behavior we can re-open it and discuss.