Not getting Likes for predated comment or reply using core_v2_activityStory API

The List Activity Stories Script API returns a list of ActivityStory, which doesn't contain a Likes property. Can you elaborate further on how you are using this method call and what you're expecting to see returned?

We are trying to get all the activities done in the community for a specific time interval. We are using the below method to get that.

core_v2_activityStory.List({ StartDate: startDateArg, EndDate: endDateArg })

For Like, if there is a predated comment/reply and we like it today, the core_v2_activityStory should fetch the particular blog/forum (whose reply/comment is liked today). That we are not getting in the above API using the correct StartDate and EndDate criteria.

So you're expecting that a Like on a content will update the activity story and push it to the top of the stream? Out-of-the-box, likes do not update activity stories in that way. Only "larger" actions like comments or replies on the content will push the activity story to the top again. More details on the actions that affect the Activity Stream can be seen in Administration > Activity Stream, viewing the Activity Story Types and Activity Story Updates lists.

This could be achieved, if desired, through custom implementation of an  IActivityStoryType Plugin Type and/or  IActivityStoryUpdateIdentifier Plugin Type . 

  do the "Status", and "Status Notes" updates for and Idea will push it to top of the Activity Story again? 

Updates to an Idea's status can bump an idea up on the Activity Story Stream if the Idea Status is enabled. Check under Pencil Icon>Administration > Activity Stream>Activity Story Updates>Idea Status to confirm this is enabled.

We have already enabled "Idea Status" under Pencil Icon>Administration > Activity Stream>Activity Story Updates>Idea Status. Still any update in the Idea status, does not bump the idea up the Activity Story Stream.

I have been able to recreate this behavior and am following up with our product team for more details.