When a user visits the dashboard of a newly-started CM instances that has hydrated actions from the DB CM serializes some of the activity info including permalink which is NOT stored in the db. Subsequently, accessing this property causes snoowrap to causes a full fetch for each activity. This drastically impacts CM api usage and performance:
number of api calls used in 1:1 with number of delayed actions
UI hangs while all activities are fetched
Solution for this is using existing Activity entity to store dispatched activity info. #136 is a partial implementation for this which also checks that Activities associated with existing Check/Run results isn't deleted after the delayed activity is run.
Delayed action entities do not store all of the associated activity's data (and don't use the existing Activity entity).
When a user visits the dashboard of a newly-started CM instances that has hydrated actions from the DB CM serializes some of the activity info including permalink which is NOT stored in the db. Subsequently, accessing this property causes snoowrap to causes a full
fetchfor each activity. This drastically impacts CM api usage and performance:Solution for this is using existing Activity entity to store dispatched activity info. #136 is a partial implementation for this which also checks that Activities associated with existing Check/Run results isn't deleted after the delayed activity is run.