Azure Data Factory UserErrorSourceQueryTimeout caused by Linked Service Azure Database for Postgresql

Question

Azure Data Factory UserErrorSourceQueryTimeout caused by Linked Service Azure Database for Postgresql

Mateusz Gródek 30

Hello,

Recently, I have encountered the following error for Lookup or Script activities when the activity takes longer than 15 minutes to complete:

Operation on target Lookup1 failed: Failure happened on 'Source' side. ErrorCode=UserErrorSourceQueryTimeout,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Query source database timeout,Source=Microsoft.DataTransfer.DataContracts,''Type=System.TimeoutException,Message=,Source=Microsoft.DataTransfer.DataContracts,'

In linked service I set CommandTimeout = 0

In activity General Timeout default = 12h (0.12:00:00)

In activity Settings QueryTimeout default = 120min

There is no statement_timeout=0 in source DB. When I run query localy it works even after 15 min.

I have a solution because after I changing Linked Service version back to "1.0" everything works correctly. However, I need version 2.0 to run Scripts activity. Any advice?

User's image

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Anonymous

2025-09-16T10:57:30.6966667+00:00
Hi Mateusz Gródek,

greetings for the day!

Here are a few things you can try to resolve this:

Linked Service Configuration: Double-check your linked service configuration, especially under the QueryTimeout settings. Even though you set the command timeout to 0, it's important to ensure that the query timeout is also set correctly. According to the PostgreSqlSource documentation, the queryTimeout must be formatted correctly (e.g., 00:30:00 for 30 minutes).

Review Version Settings: You mentioned that switching back to version 1.0 resolved the issue. This suggests that the newer version may have different default settings or limitations. Check the release notes for version 2.0 to see if any timeout-related changes were made.https://learn.microsoft.com/en-us/azure/data-factory/connector-postgresql?tabs=data-factory#differences-between-postgresql-and-postgresql-legacy

Adjust QueryTimeout: If you're consistently running longer queries, try setting the QueryTimeout to a higher value within your ADF activity settings. It's common to hit timeouts if the queries take longer than expected.

Database Performance: Since your query works locally but fails in ADF, it could be beneficial to check your PostgreSQL performance, especially resource availability.

Network Considerations: Ensure that there are no network issues causing problems when ADF tries to communicate with your PostgreSQL database, especially if using private endpoints.

Try adding SET statement_timeout = 0; at the beginning of your query in ADF Script/Lookup activity.

Here is the document for Linked service properties of V2 connector

https://learn.microsoft.com/en-us/azure/data-factory/connector-postgresql?tabs=data-factory#linked-service-properties

Can you please confirm if you are still getting the same query timeout error when using the Azure subscription, instead of manually entering the details?And try to use Azure key vault instead of directly giving the password.

Please let us know if you have already tried this and are still experiencing the same issue.

Thanks!

Kalyani
Mateusz Gródek 30 Reputation points

2025-09-16T12:54:24.5033333+00:00
Thank you for answer.

Where Can I set QueryTimeout in Linked Service Configuration? There is no such a properties in documentation and Linked Service configuration

I checked this before sending the request but couldn't find an answer.

I set it to default which is 2 hour:

I tested it using simple function:

create function long_waiter() returns void language plpgsql as $$ BEGIN PERFORM pg_sleep(1000); END; $$;

there is no network problem because v1.0 works fine

6.**SET statement_timeout = 0; It didn't help.
**
Have you tested this on your end?
Anonymous

2025-09-16T14:19:27.42+00:00

Hi Mateusz Gródek

Thank you for your response!

I tried to reproduce the issue from my end:

I haven't faced any issues while using script activity with sample creation table script.

Linked service configuration: I have used the select method as from azure subscription method

Thanks!

Kalyani
Mateusz Gródek 30 Reputation points

2025-09-17T07:10:02.4033333+00:00

Thank you for testing it. Did you check the script that will run for 16 minutes? Because then an error appears.
Anonymous

2025-09-17T08:25:28.2666667+00:00

Hi Mateusz Gródek,

Greetings for the day!

Could you please check the private message? At the moment, I don’t have a code sample that runs for more than 15 minutes. Could you also elaborate on what you are using in the script and lookup activities? Additionally, can you confirm if your linked service connection is successful, and in which environment you are facing this issue?

Thanks!

Answer accepted by question author

1 additional answer

Mateusz Gródek 30 Reputation points

2025-09-16T12:54:24.5033333+00:00

Thank you for answer.

Where Can I set QueryTimeout in Linked Service Configuration? There is no such a properties in documentation and Linked Service configuration

I checked this before sending the request but couldn't find an answer.

I set it to default which is 2 hour:

I tested it using simple function:

create function long_waiter() returns void language plpgsql as $$ BEGIN PERFORM pg_sleep(1000); END; $$;

there is no network problem because v1.0 works fine

6.**SET statement_timeout = 0; It didn't help.
**
Have you tested this on your end?
Anonymous

2025-09-16T14:19:27.42+00:00

Hi Mateusz Gródek

Thank you for your response!

I tried to reproduce the issue from my end:

I haven't faced any issues while using script activity with sample creation table script.

Linked service configuration: I have used the select method as from azure subscription method

Thanks!

Kalyani
Mateusz Gródek 30 Reputation points

2025-09-17T07:10:02.4033333+00:00

Thank you for testing it. Did you check the script that will run for 16 minutes? Because then an error appears.
Anonymous

2025-09-17T08:25:28.2666667+00:00

Hi Mateusz Gródek,

Greetings for the day!

Could you please check the private message? At the moment, I don’t have a code sample that runs for more than 15 minutes. Could you also elaborate on what you are using in the script and lookup activities? Additionally, can you confirm if your linked service connection is successful, and in which environment you are facing this issue?

Thanks!

Answer 1

Hi Mateusz Gródek,

Greetings for the day!

Following upon our discussion over private messaging.

After checking with our internal team, I would like to share that this is a known issue with the Azure PostgreSQL V2 connector related to query timeouts.

Resolution / Next Steps:

For customers using Azure IR, our product group is planning to release the fix in the next regular deployment cycle, scheduled to begin in early October. Since the rollout usually takes 1–2 weeks across all public regions, the fix should be available by the end of October.
For customers using SHIR, the product group has provided an estimated timeline of mid-November for the fix.

We understand this may cause inconvenience, and we truly appreciate your patience while our team works to resolve this in next deployments.

I hope this information has been helpful!

Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered.

If this answers your query, please click Accept Answer and Upvote for was this answer helpful.

Thanks!

Kalyani

Mateusz Gródek 30 Reputation points

2025-09-22T08:31:01.8866667+00:00

Thank you
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 2

Hello Mateusz Gródek,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that your Azure Data Factory UserErrorSourceQueryTimeout caused by Linked Service Azure Database for Postgresql.

The following steps can help you to resolve the issue:

Step 1: Set scriptBlockExecutionTimeout in the script activity to a high value:

"scriptBlockExecutionTimeout": "02:00:00"This controls how long each script block can run. - https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-data-factory-script-activity-azure

Step 2: In the activity policy section of the json file: "timeout": "1.12:00:00"This sets the overall timeout for the activity. - https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-data-factory-script-activity-azure.

Step 3: Ensure the following in your Linked Service JSON to use Correct Linked Service v2.0 Configuration:

"commandTimeout": 0,
"connectionTimeout": 600,
"pooling": false,
"noResetOnClose": true

These settings help avoid premature termination and connection reuse issues. - https://learn.microsoft.com/en-us/answers/questions/2044922/adf-postgresql-linked-service-connector-settings

Step 4: Avoid hardcoding passwords. Use:

"password": {
  "type": "AzureKeyVaultSecret",
  "store": {
    "referenceName": "<KeyVaultLinkedService>",
    "type": "LinkedServiceReference"
  },
  "secretName": "<your-secret-name>"
}

This ensures secure and stable credential handling. - https://learn.microsoft.com/en-us/azure/data-factory/connector-postgresql

Step 5: Use Self-Hosted Integration Runtime (SHIR) if your PostgreSQL is behind a firewall or VNet, SHIR will help to avoid network timeouts. - https://learn.microsoft.com/en-us/azure/data-factory/connector-postgresql

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mateusz Gródek 30 Reputation points

2025-09-17T12:22:13.6533333+00:00

Thank you for answer. I got information that this may be an error from Azure team side. So I'm waiting for verification.

Share via

Azure Data Factory UserErrorSourceQueryTimeout caused by Linked Service Azure Database for Postgresql

1 additional answer