AIOBlock

[nicksigley]

Hello

Since our server migrated from on-premises to the cloud, I am experiencing issues with Alteryx. One such issue I cannot find any information about online. Please see image, but it reports AIOBlock. The workflow is blocked, and progresses partially, but never finishes. Does anyone have any information about what this error means or how to solve it?

Many thanks

[caltang]

You migrated this workflow to the Server or to your own virtual machine? Sorry, wasn't clear. Reaching out to Alteryx Support via Mission Control is much better - they'll ask for your Alteryx version and logs. Have you done so?

[nicksigley]

The workflow, and the files it connects to, were migrated to the cloud server. If I put all the files on my own computer I don't get the error.

Thanks re. Support, yes, we have in parallel reached out to them

[caltang]

I'm just throwing it out, could be your cloud settings preventing Alteryx from reading the files for use - have you checked if there's any requirements to whitelist?

[bkclaw113]

@nicksigley did you get a resolution to the error?

[nicksigley]

Not as yet and not on this forum. It's been with Alteryx support for a while and we don't have anything definitive from them yet.

[bkclaw113]

We were not able to figure out the why, but suspect it was related to a macro (connector to HR System - Bamboo) that was built on 22.3 and loaded to the server. Then the server was upgraded to 23.2. To mitigate the issue we pulled the workflow off of the server, opened and saved the macro in designer 23.2, then deleted and re-added the 23.2 version of the macro into the workflow and saved it back up to 23.2.

It seemed to do the trick.

[nicksigley · Accepted solution]

For anyone else who has experienced this problem, it looks like it was finally solved with the help of Alteryx.

3 parts of the solution:

1. Download and install the patch released 8th December 2023, 2023.2.1.51 (Patch 1)

2. Disable AMP engine in settings

3. Disable AMP engine in saved workflows