Process Failure with CloudWorks

aakash
Frequent Contributor

Process Failure with CloudWorks

Hi,

I am trying to automate a model to model import with cloudworks, the process fails and I am observing some strange behaviour

1. The same process runs for dev model but fails for prod model. Both models are in sync. While running the process manually, it completes successfully in both models.

2. My process has 4 actions in totals, however when I am viewing details of failure in cloudworks I can see only 3 actions, but if I click on edit, the 4 actions are intact.


Attaching the error screenshot

aakash_0-1630675484779.png

 

Does anyone has any idea on how to resolve this and what could be causing this error? Any help is appreciated

 

Thanks and Regards,

Aakash Sachdeva

1 ACCEPTED SOLUTION

Accepted Solutions
aakash
Frequent Contributor

Re: Process Failure with CloudWorks

Hi @andrewtye @rob_marshall ,

 

Thanks a lot for the help. I have found a solution (workaround) for this failure. This is going to be very helpful for anyone encountering this error where the same process runs in development model but not in deployed model using cloudworks. Had been investigating the cause of this failure and below are my findings. 

Cause of the Issue

1. When you create an import from the same model as source and target , and later sync this to target. The import data source is not populated correctly.

2. After the sync , if you navigate to 'Import Data Source', for the same import in the Production Model , the column with the 'Source Model' would still have the name of Dev Model stored in it.

3. When you run this import manually in the model itself, somehow the model recognizes that the import source and target are meant to be production model only, but the same import when ran through cloudworks would see this data source field (I assume) and it always tries to run the import considering the dev model as a source, which causes the issue here. I have checked , even the imports which are running fine only reflect the data coming in from Dev Model , not the Production Model. Since, this is the same model, you cannot even edit 'Source Data Models'. 

 

Workaround

1. Navigate to Dev Model , Mark these import data sources as production imports.

2. Create a revision tag and sync to Production Model.

3. Visit the Production Model and edit these sources to correctly reflect the production model, once that happens , the source Model field will become blank.

4. Your process should work now using cloudworks.

 

@rob_marshall , feel free to add to this and maybe we can add this to 'Known Issues and Workarounds'?

 

Hope this is going to help others

Regards,

Aakash Sachdeva

View solution in original post

7 REPLIES 7
rob_marshall
Moderator

Re: Process Failure with CloudWorks

@aakash 

 

Quick question, from CloudWorks, are you using the same user ID?  My thinking is around security and your ID  has the appropriate security and the ETL user ID does not.

 

Rob

aakash
Frequent Contributor

Re: Process Failure with CloudWorks

Hi @rob_marshall ,

 

Thanks for the quick response. I am using the same user ID for both manually running the process and for using cloudworks. Also, I am able to run other processes for the same workspace and same user access.

andrewtye
Master Anaplanner/Community Boss

Re: Process Failure with CloudWorks

Hi @aakash 

We've got the same issue ... and it's a known problem with integrations within Cloudworks.

This thread has the answer from @DibB (https://community.anaplan.com/t5/Anaplan-Platform/Experience-with-Cloudworks-model-to-model-integrat...) and to them is there an update as to when it'll be deployed?

Andrew

aakash
Frequent Contributor

Re: Process Failure with CloudWorks

Hi @andrewtye @rob_marshall ,

 

Thanks a lot for the help. I have found a solution (workaround) for this failure. This is going to be very helpful for anyone encountering this error where the same process runs in development model but not in deployed model using cloudworks. Had been investigating the cause of this failure and below are my findings. 

Cause of the Issue

1. When you create an import from the same model as source and target , and later sync this to target. The import data source is not populated correctly.

2. After the sync , if you navigate to 'Import Data Source', for the same import in the Production Model , the column with the 'Source Model' would still have the name of Dev Model stored in it.

3. When you run this import manually in the model itself, somehow the model recognizes that the import source and target are meant to be production model only, but the same import when ran through cloudworks would see this data source field (I assume) and it always tries to run the import considering the dev model as a source, which causes the issue here. I have checked , even the imports which are running fine only reflect the data coming in from Dev Model , not the Production Model. Since, this is the same model, you cannot even edit 'Source Data Models'. 

 

Workaround

1. Navigate to Dev Model , Mark these import data sources as production imports.

2. Create a revision tag and sync to Production Model.

3. Visit the Production Model and edit these sources to correctly reflect the production model, once that happens , the source Model field will become blank.

4. Your process should work now using cloudworks.

 

@rob_marshall , feel free to add to this and maybe we can add this to 'Known Issues and Workarounds'?

 

Hope this is going to help others

Regards,

Aakash Sachdeva

View solution in original post

rob_marshall
Moderator

Re: Process Failure with CloudWorks

@aakash 

 

That is a great call and it may in fact work, but in my eyes, it shouldn't BE the solution.  You said it best, it is a work around.  Let me see what I can find out about this on this side and will get back to you.

 

Don't get me wrong, I am a huge of clean Import Sources, but making them Production Data is not correct.

 

Rob

andrewtye
Master Anaplanner/Community Boss

Re: Process Failure with CloudWorks

I did think that this was possible but then remembered those sage words "just because you can doesn't mean you should"

Hope the proper fix comes in soon.

DibB
Occasional Contributor

Re: Process Failure with CloudWorks

We have put in a fix for the issue. Can you please let us know if the issue still exists?