Issue when using Block Until Done and Power BI Tool together (AMP Engine dilemma)

Question

Hello,

I'm experiencing issues when I use the Block Until Done tool and the Power BI Tool together.

My workflow starts with the extract of several SAP Tables through the DVW ACS Connector.

Tables are joined altogether before facing some data processing procedures through several workflow streams, separated with Block Until Done tools.

If AMP Engine is activated, the Block Until Done gives a "memory limit" message and the data are stopped there.

If AMP Engine is deactivated, the Block Until Done doesn't give any problem, but the PowerBI Tool doesn't work because it needs the AMP Engine to work.

Do you have any suggestion on how to solve this?

Thank you,

Alberto

nbondarchuk · Answer

@AlbertoRefra Using Control Container is definitely a good workaround.

That said, we’d like to understand why this works with the E1 Engine but not with AMP. It could be related to the engine itself, the SDK, or possibly a connectivity issue.

If you’re able to, please create a small workflow that reproduces the issue and submit it as a defect. That will help us dig into the root cause and work on a fix.

Thanks again - we really appreciate your help!

jrlindem · Answer

@AlbertoRefra

To @binu_acs point, you should switch to Control Containers, especially since you're having to use AMP.  AMP runs concurrently which tends to mess up the Block Until Done tool due to this multi-thread behavior, but Control Containers will help ensure proper sequencing.

Here's an article to help you learn more about Control Containers:  Tool Mastery | Control Container - Alteryx Community

WirkKarl · Answer

Hi! This is a tricky one since the AMP Engine is required for the Power BI Tool but seems to conflict with the Block Until Done tool. One approach that sometimes helps is breaking your workflow into smaller chunks so each Block Until Done doesn’t handle too much data at once, which can reduce memory usage. Another option is using the In-Database tools or caching intermediate results to ease the memory load. You might also consider reaching out to Alteryx support they’ve seen similar AMP-related memory issues and may have a workflow-specific workaround.