ADF pipeline to Salesforce fails in Trigger mode, but runs in Debug mode

Hi Venkat,

Thanks for your reply. Unfortunately, it is not actually the connection to salesforce that fails. I am already using Client Id and Secret to connect to Salesforce. The test connection in the Liked Service works successfully. I am also able to successfully run the ADF pipeline in debug mode. But when I trigger the pipeline, it fails with the error I mentioned.

It stopped working since I made a change to another pipeline and published the changes. To me, it feels some mismatch between the published version and the main branch. However, I do not have any local branch. I am working on the main branch for both debug and trigger runs. I can also see under branches, an ADF_Publish branch. I thought this is an internally created branch and usually hidden.

Thanks,

Sindhu

Hi SW

Thank you for your response, and I truly appreciate your patience. I understand that this issue is frustrating, especially since the connection works fine in Debug mode but fails in Trigger mode.

Regarding your feedback, I apologize if my previous response did not fully address your concern. My goal is to provide the best possible support, and your feedback is valuable in helping us improve.

Mismatch Between Main Branch and ADF_Publish

The ADF_Publish branch is automatically created by Azure Data Factory to store the published artifacts.

Even though you’re working on the main branch, triggered pipeline runs execute based on what is in ADF_Publish rather than the main branch.

There could be a mismatch between your main branch and ADF_Publish. Try re-publishing all pipelines to ensure consistency.

Authentication Differences in Debug vs. Trigger Mode

Debug mode runs under your user credentials, while a triggered run may use a managed identity or service principal for authentication.

Ensure that the authentication method used during Debug mode is the same as the one used for Trigger runs.

If using a managed identity, confirm that it has the necessary permissions in Salesforce.

Check for Expired or Revoked Credentials

Even though Debug mode works, the triggered run might be using a different authentication method or an expired access token.

Try recreating the Linked Service in ADF to refresh the authentication details.

If using OAuth, ensure the token has not expired and that the connected app in Salesforce is correctly configured.

It stopped working since I made a change to another pipeline and published the changes

Since the issue started after modifying another pipeline, try rolling back the recent changes and republishing to see if the error persists.

Verify if there are any parameters or variables that behave differently in Debug vs. Trigger mode, which might impact authentication or data movement.

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

SW We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Thank you Venkat. I am looking at these options now.

• Compared the ADF_Publish and the Main Branch's json files using Diff difference. they are absolutely the same.
• Credentials have not expired, as confirmed by Salesforce person.
• Re-created the linked service. Tested connection. All good
• The linked service used Secret Id and Password, not using any tokens.
• Deleted and re-created the trigger.

Unfortunately none of the above made any difference. Now, as you suggested, I need to revert the changes I made to the other pipeline. That is quite a lot of changes since the purpose was a clean-up of all the ADF pipelines. I will do that and let you know the outcome.

Thanks for your help