Record packets locked at the end of the run?

[warrencowan]

Hi All, 

Am running a workflow as with multiple batch macros with AMP enabled, and at the end of first macros, it reports an error, citing 

" Designer x64 The Designer x64 reported: Record packets locked at the end of the run: 1" ... and brings the whole workflow to a stop.

All the messages and post run checks indicate that all inputs were successfully read and all outputs successfully written to, yet the workflow errors, and thus prevents the reminaing macros from progressing.

I cant find any info on this error though. does anyone know what it means and how to resolve?

thnx

w

[TonyaS]

@warrencowan 

Thank you for the early feedback on the new AMP Engine. 

I encourage you to continue to report any use case issues that you find with running workflows with AMP Engine enabled. We worked hard to identify differences from the original Engine as well as provide guidance on how to better optimize workflows to run with AMP. 

If you haven't already, please review our articles related to using the new AMP Engine:

https://help.alteryx.com/current/designer/alteryx-amp-engine

https://help.alteryx.com/current/designer/Alteryx-Engine-and-AMP-Main-Differences

https://help.alteryx.com/current/designer/AMP-Memory-Use

https://help.alteryx.com/current/designer/tool-use-amp

https://community.alteryx.com/t5/Engine-Works/AMP-Engine-Technical-Deep-Dive-Part-1-Why-AMP/ba-p/570...

https://community.alteryx.com/t5/Engine-Works/AMP-Engine-Technical-Deep-Dive-Part-2-Key-concepts-of-...

https://community.alteryx.com/t5/Engine-Works/AMPlify-your-Workflows/ba-p/617590

We have started looking at this to see how we can help.

If you could provide a sub-set of the workflow that demonstrates the issue that would be helpful. 

[vishnuharinarayanan]

Helloo,

I have also faced the same error while using a workflow with AMP engine having a Batch macro in the canvas. Can you help me in solving the issue?

[warrencowan]

Thnx @TonyaS  , I've trawled the docs many times (and they are excellent intros btw) but there's nothing in there that has led me towards anything that could solve the issue.

I would happily share the workflow here, but I am a tad reluctant as its quite hard to decouple the offending item from such a significant set of flows, and the time it would take it do physically, much less to ensure I have removed anything sesntitive or dependent makes me wary. 

Do you have another suggestion.

many thnx w

[TonyaS]

@warrencowan 

In order for us to try to identify the root cause of the issue, it would be nice to have shortcut of this WF, it could be enough to have an input to batch macro that errors and the batch macro itself. If you can't provide the WF itself, it would be very helpful to see screen shots of those parts. We need this to understand the flow of the data. You can send them to me in a private message or email if you prefer. 

[Harley]

@TonyaS 

I am getting the same issue on both 2020.3 and 2021.1 builds.

Has there been any effort in resolving this? It's a bit frustrating as AMP has been release for a few releases but my organization cannot take advantage of it due to these errors that are impossible to debug.

[TheOC]

Hey @Harley 
Are you able to share with me a workflow that presents this issue? And I'll try to have a look at why its being caused.

AMP is still classed as a 'new' feature, and so its still going to experience some issues, but if you manage to recreate an issue I'd recommend also creating a ticket on the bug reporting side of the support:
https://community.alteryx.com/t5/forums/postpage/board-id/@support

Here Alteryx Support will help you, and investigate the issue internally.

Thanks,
TheOC

[TonyaS]

@Harley 

We have made improvements to prevent Deadlock errors.  A fix specific to Grouping and Blocking tools was released in 21.1 and a fix that included enabling action order for Summarize and increasing the number of threads if memory is increased was released in 21.2. We have a third improvement that should prevent most remaining Deadlocks scheduled to be released in 21.3.   I would suggest waiting for the 21.3 and then if you are able to upgrade I would expect your issue to be fixed.

In the meantime, if you are able to supply your workflow as a yxzp that reproduces the issue you are seeing I would be happy to try it on our latest build version to see if it is fixed. You can send me a private message and we can set up a secure way for you to transfer the workflow. 

[MeghanGohil]

Hi Tonya - we are still experiencing this issue as well.  It's a batch macro.

[TonyaS]

@MeghanGohil  are you saying you are still seeing the issue on the 21.3 version? That is the version that has the deadlock fixes.