jsmith141
New Contributor III
Joined 4 years ago
User Profile
User Widgets
Contributions
Question Regarding Scheduled Task cron First Tuesday of the month
I have a pipeline that needs to run on the first Tuesday of every month. Looking at the details indicates that the scheduled task should execute as expected, see below… However, the task never executed. Any insight as to why this task did not execute as expected would be appreciated. I have included a screenshot of the cron summary below as well Thanks, James1.1KViews0likes0CommentsQuestion about "Trust All Certificates" Option in REST GET Snap
Hi, Please forgive my ignorance in this subject matter, but I have created a few basic APIs in the APIM from existing pipelines. When I try to call them using a groundplex secure URL in a REST GET snap, the only way I can get a successful call is to check the box “Trust all Certificates”. Can anyone provide me any guidance or recommendations in a scenario like this one? Please let me know if any additional information is needed. Any insight/best practices for this option would be much appreciated. Thanks, James946Views0likes0CommentsRe: Passing Body Content in Post Snap
Okay I enabled that yesterday afternoon. So far on the Ring Central side, the 401 errors have diminished. In fact today(03/18) there is a 100% success rate running that pipeline every 59 minutes. This may be an obvious question and I think I know the answer, but just for clarification, with the auto refresh enabled does that enable a background process to run on the account to refresh the token at the needed interval to prevent the account from having an expired token (independent of the state of a specific pipeline that may utilize that account)?698Views0likes1CommentRe: Passing Body Content in Post Snap
Because I chose password for the grant_type, I did not check the auto refresh token option. Could that be the reason I see 401 errors on the RingCentral side? It looks like the it retries 3 times on the SnapLogic side. So could it be the 401 is being thrown because it tries to use the token it already has, but it is expired, so then requests a new token and all we see on the SnapLogic side is a successful run because after getting a new token on the 2nd try, everything works.695Views0likes3CommentsRe: Passing Body Content in Post Snap
Sorry for the delay in response. Would the OpenAPI snap help us avoid some of the 401 errors I am still seeing on the RingCentral app analytic side? In order for an app to be promoted into production it has to have a <5% 4XX return code on all used end points for that app. I have this pipeline set to run every hour, but it looks like the call frequently fails with a 401, but then it retries and is successful, as best as I can tell. Please let me know if this needs to be a different thread. I just noticed this morning that we are not meeting this last requirement. Thanks, James921Views0likes6CommentsRe: Passing Body Content in Post Snap
As I was typing the ticket out, I realized that I was making an endpoint call using a POST snap that should have been a GET snap. With the type of account we used (an Ouath2.o account) I no longer needed the post snap at all. I did not realize that until now. The way we have always built these pipelines out is to setup a POST snap to get a token back, but this account type takes care of that for you Once I compensated for that fact and switched to a GET snap with the same account, it worked as expected. Thank you both so much for all of your help. I apologize for getting mixed up and hanging on to the POST snap like that and that it took me so long to realize what was going on at the end there. Again thank you @ddellsperger and @ptaylor! Best, James921Views3likes8CommentsRe: Passing Body Content in Post Snap
No the permission scope is set in the application that you create on the RingCentral side and then you are provided with a client ID and secret for the application. Is there a way to convert this post to a ticket? There is a lot of relevant information here.733Views0likes10CommentsRe: Passing Body Content in Post Snap
Okay I get the same permissions error when switching back to a password grant type. I have to stress that this does not happen when I follow the process in Postman, which leads me to believe that it is on the snapLogic side, or something between the data exchange specifically with the snapLogic post snap and RingCentral. I also have to point out that this permission is not even an option in RingCentral. Finally the idea of just giving full permissions to the app in Ring Central is problematic, because in order to promote your app from the Sandbox to Production you have to test all permission scopes explicitly on top of meeting additional criteria before your app is eligible for promotion to production. So we really dont have the option of of giving a broad scope of permissions. Even if it did work, it leads to potential problems down the road. Do we need to start looking at converting this thread into a ticket and escalating it?733Views0likes12CommentsRe: Passing Body Content in Post Snap
Okay that is one difference (the fact that you use the token endpoint for both OAuth2 Endpoint and token fields) that I see you did that I had not done when I was trying to get the password grant type to work. I have everything switched back over on the RIngCentral side. Do I still need to have the Auto-refresh token enabled on either side? Also do I need to click the authorize button when I edit the account and change back to password grant type (it doesn’t seem like I would need to click that button)?736Views0likes0Comments
Groups
Higher Ed Users Group
This user group is for customers within higher education.0 Posts
