refresh token pipeline parameter runs successfully during manual trigger but not scheduled trigger

Question

I have an ADF pipeline set up with LS_RestServiceNetSuite.

Within the pipeline there is a web activity "Get_Access_Token" that has started to fail.

In this activity, in the URL field we passed:

                     "@pipeline().globalParameters.Access_Token_URL"

This URL is the access token URL which we have stored as a global parameter

Then we are using the POST method of HTTP and sending the below code in the body:     "@concat('grant_type=refresh_token&refresh_token=',pipeline().parameters.Refresh_Token)"

This basically contains the refresh_token which we will be passing as a pipeline parameter.

Currently, we are manually pulling the refresh token via Postman. I am able to pull a authorization code to put in Postman, and generate a refresh token. The refresh token is put in as parameter of the pipeline. When I manually run the trigger it is successful. However, when the scheduled trigger runs with the refresh token, the "Get_Access_Token" web activity fails.

We have been troubleshooting for the past week. Help is appreciated.

Answer 1

Based on this old thread :

My understanding is it's possible that the scheduled trigger encounters issues due to the state of the data at the time of execution. Also check the time zone settings of your scheduled trigger and ensure that it aligns with your expectations. Please check input parameters or values being used in the lookup activity. Make sure they are correct and within the expected range. I have scheduled a pipeline that moves data from SQL database to Azure Datalake storage.