Issue with storing the data when parsing through workflow on a list

We are working on a automation that extracts activities through api call from a linkedIN user profile,.




In the above the data I am getting from the backend is a list of activites with different parameters. I can see in the logs when extract activity gets scheduled, that a member is passed, since its shows the member id their, but it is not getting saved in the backend in the activity creation workflow, other two data types are getting stored. And member is critical to our working of other workflows.

I have added similar workflows for the same on the other automations, and they are working, any chance of bug here or something we are missing?

Couple of things you can do to figure out WHERE the issue is.

  1. In the extract activity list workflow, add a step to email yourself the “member” value. (You could also check the logs). If you’re not receiving it here, you might have to double check your mapping.

  2. In the activity creation workflow, test the same as #1. If #1 is working properly and #2 isn’t, make sure your “member” value is the right data type and being sent properly.

Sometimes, removing and recreating a parameter does the trick.

To be honest, I couldn’t find the member id in the raw code you shared but I’ll take your word that it’s there.