topic Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection in Dataflow

00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

rtylerr — Mon, 03 Nov 2025 14:19:57 GMT

Hi all

I connect to my redshift cluster through a gateway, the data loads in dataflow preview, then when I go to refresh in the workspace i get an error, a random activity id throw up in the excel output - and it usually is 00;31 seconds before it fails everytime.

Is this a gateway issue?

Helpppp

Thanks

Rob

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

tayloramy — Mon, 03 Nov 2025 14:54:20 GMT

HI rtylerr,

Can you give us some more details? Do you have any error messages you can share?

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

Anonymous — Thu, 06 Nov 2025 05:55:25 GMT

Hi rtylerr ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

Since the preview loads but the refresh consistently fails around 00:31 seconds, this usually suggests a network timeout on the gateway path rather than an issue with Fabric Dataflow. Please check the gateway host's firewall or proxy settings and make sure there isn’t a 30-second idle or session timeout for outbound connections to Redshift. Dataflows Gen2 has better network management, so switching to Gen2 is recommended if possible.

Thank you.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

Anonymous — Mon, 10 Nov 2025 05:12:42 GMT

Hi rtylerr ,

I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

Thank you.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

rtylerr — Mon, 10 Nov 2025 09:18:27 GMT

Thanks all for your help. I've given this information to the IT admin who has access to the gateway to try troubleshoot. What is annoying is that this was all fine when we first connected a few weeks back.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

Anonymous — Fri, 14 Nov 2025 04:38:05 GMT

Hi rtylerr ,

Thanks for the update. Could you please let us know if the issue has been resolved? If you still require support, please let us know, we are happy to assist you.

Thank you.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

rtylerr — Mon, 17 Nov 2025 09:18:48 GMT

Is there a particular reason why PPU would work on a gen 2 dataflow but it would not on a Pro Gen 1? My IT admin has made it PPU and re-worked it and now it works. but this isn't helpful for the end-state as my end-users not all have PPU.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

rtylerr — Mon, 17 Nov 2025 09:19:44 GMT

sorry, I think PPU also works on gen1

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

Anonymous — Sat, 22 Nov 2025 01:37:24 GMT

Hi rtylerr ,

PPU itself wouldn’t resolve a gateway timeout. PPU only impacts feature access, not connectivity. The refresh succeeding after the move likely happened because the dataflow was rebuilt and reconfigured during the transition, which created a new connection path. The underlying issue is still related to the gateway or network settings. Once those are finalized, the same dataflow should refresh normally in a Pro/Gen1 workspace without needing PPU.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

Anonymous — Mon, 01 Dec 2025 05:14:01 GMT

Hi rtylerr ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

R1k91 — Thu, 04 Dec 2025 11:29:29 GMT

are you sure you can create a dataflow gen2 in PPU workspace? I don't think so.
if it's a premium/fabric capacity you can.

gen 2 gives you the possibility to switch to "Fast Copy" that behind the scenes changes the runtime from dataflow to data factory copy activity runtime. this can give you the idea you're running dataflows but in reality you're running a data pipeline.

with a customer we had an issue of dataflow not able to complete if fast copy was enabled and able to complete if it was disabled because of different management of TLS protocol. AFAIK this had been solved and they now both use the same TLS version but the concept is again you think it's a DF and in reality is a pipeline.
Fast copy in Dataflow Gen2 - Microsoft Fabric | Microsoft Learn

Re: 00;31 second failed timeout for Dataflows Gen 1 with Redshift Connection

rtylerr — Fri, 05 Dec 2025 09:22:15 GMT

Since then admin has put us onto a fabric sku and it's all fine now. Not a clue why but already now I have a space where end users can view reports and the data flows are working!