StreamFeed.removeActivity returns successful response but appears to remove the activity async.

Repro Steps:

1. Using connected stream-js client, create an instantiated StreamFeed object.

const feed = streamClient.feed('some-feed-name', 'some-stream-user-id);

1. Find activity

const beforeRemoveResponse = await streamClient.getActivities({ ids: ['some-activity-id']});

feed.removeActivity(beforeRemoveResponse.results[0].id);

const afterRemoveResponse = await streamClient.getActivities({ ids: ['some-activity-id']});

Expected Behavior: The afterRemoveResponse result is empty, as I’ve removed the activity and Stream gave me 200/OK Http response code.

Actual: The activity is still there for some amount of time.

I guess this could be expected behavior or a result of caching, however it is undocumented and coupled with the fact that length of processing appears to vary from near instantaneous to minutes it is something that has sucked up some of my time and not friendly.

gz#7877

[ferhatelmas]

What you did in the snippet is receiving built group id for an aggregated/notification feed. That id is pseudo id generated from aggregation format. That’s why activities inside a group is dynamic as new ones are coming and can be changed with ranking too. You don’t want it in general because its usage very limited, IMHO.

Use real activity id or foreign id/time pair on client if you want to fetch specific activities. From your snippet, 80204172-3665-11eb-a9c2-0ae838defca7 is the id. client.getActivities({ids: [your_id]})

[ferhatelmas]

@shiivan this is expected. Activity is removed from the associated feed so users can’t get it but admin (server-side) can always receive activities, they aren’t removed.

To confirm, you can read the feed and removed activity won’t be there.