Issue with Block Until Done

Hi all,

I have a workflow that writes a set of records to SQL. It should first write records in the "Update; Insert If New" container, and after that is done it should continiue with the "Write Log" container. I've set up a Block Until Done tool as displayed in the screenshot, but when I run the workflow it does not pass any data through it. It stops at the select tool before the Block Until Done tool, and the result window says "Memory limit reached. Use a Browse tool to view full results". I've overridden the memory limit on both tool and designer level, so this is not the issue.

Any thoughts?

Output

Accepted answers

apathetichell

Two things- what database type are you writing to - and is AMP on - if so - can you toggle it off?

All comments

Cesc

Hi ,

If you are experiencing the "Memory limit reached" error message in Alteryx, you may need to adjust the memory settings for your workflow or for the Alteryx Designer application itself.

To adjust the memory settings for your workflow, you can follow these steps:

Open your workflow in Alteryx Designer.
Click on "Workflow" in the top menu bar and select "Workflow Configuration".
In the "Workflow Properties" window, click on the "Runtime" tab.
Under "Memory usage", you can adjust the "Memory quota" setting to increase the amount of memory allocated to your workflow. You can also enable the "Auto Configure Memory" option to let Alteryx automatically adjust the memory usage based on the available system resources.

To adjust the memory settings for the Alteryx Designer application, you can follow these steps:

Open Alteryx Designer.
Click on "Options" in the top menu bar and select "User Settings".
In the "User Settings" window, click on the "Advanced" tab.
Under "Engine Settings", you can adjust the "Default Memory Quota" setting to increase the amount of memory allocated to the Alteryx Designer application.

Keep in mind that increasing the memory usage may not always solve the issue. You may need to optimize your workflow or break it down into smaller workflows to reduce the amount of data being processed at once. Additionally, if you are working with very large datasets, you may need to consider using a different data processing tool or approach that can handle larger amounts of data more efficiently.

Please also keep in mind that for what you explain, it could be an issue of missconfiguration of the Block Unitl done tool.

Trailduck

I have tried both of these with no luck. The dataset is no more than ~500 records, so it's super lightweight.

Cesc

Oh wait, what about using the browse tool as it is asking in the screenshot?

Trailduck

No luck by doing that either.

apathetichell

two questions. what happens if you toggle off one container?

If you use a browse tool can you see the results?

Trailduck

Still same result. Seems like nothing is going through the Block Until Done tool.

darryl5280

Use only 1 output connection on the "Block Until Done" tool and then connect them in order you want your output connections to run.

apathetichell

Two things- what database type are you writing to - and is AMP on - if so - can you toggle it off?

Trailduck

Surprisingly it worked when I disabled AMP in the workflow settings.

apathetichell

Can you mark my solution as correct - "turn off amp" is one of my usual first suggestions - so sorry for the delay.

masonm

I had this same issue, was getting a "memory limit reach - use browse tool" message whenever I tried to view browse tabs near the end of my workflow. I added browse tools - no data was being written to the browse tools.

I turned off AMP as suggested by @apathetichell and ran the workflow and it ran normally and I did not encounter the error. I never had this issue on 2021.2, only when I updated to 2022.3. I had previously changed both my designer settings and the workflow runtime settings to utilize more memory, but this did not fix the problem.

ACW

Issue started on my machine after upgrading SW. All my old workflows no longer run... grrrrrrr

BetoZM

May I ask how toggling off AMP would help?

apathetichell

@BetoZM How or Why? Turning off Amp works in some versions with BUD issues because BUD expects a singular thread. Ie it waits until X is done before doing Y. In a multi-thread approach X is never told that Y is done so it just hangs. I see this in situations with workflow errors and BUD tools where instead of flagging the error the workflow just hangs.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703