Thanks. I was able to get in.
I printed out the full exception that was coming back from LinkedIn.
Not enough permissions to access: partnerapiorganizationacls.finder-roleassignee....
I found a related post online about someone having a similar problem which details a LinkedIn token caching problem.
stackoverflow.com/questions/77847103/lin...ermissions-to-access
So while I was printing out the channel exception in the backend, the LinkedIn calls randomly started working for me (without any real code changes), which supports the idea that there was a token issue that got stuck. I took out the debugging statement and am able to see your posts.
I will be including the code I gave you that switched to the newer LinkedIn endpoints in the next release, since the older v2 ones will be sunset.
Weird issue, but I think it should be good now for you.
-Melissa