Unable to migrate WF to new server

[BonusCup]

Hello,

I'm trying to migrate a couple test WFs from our sandbox server to our Prod server.  Both sandbox WF's checkboxes are checked for "Ready to Be Migrated".

I have a WF using the /webapi/v3/workflows/{appID}/package endpoint that downloads the .yxzp to %Engine.TempFilePath%.  Following the instructions at Publish Workflows in the Target Environment, Step 3 and using the Swagger POST /webapi/admin/v1/workflows I'm running into the below error:

500: { "message": "An error has occurred." }

Has anyone ran into this and what was the fix if you were able to?  I'd also like to continue using Designer for the POST endpoint, how do I call that file back from the temp location to push it to the Prod server?  TIA

[abacon]

@BonusCup Did you try to use your owner ID instead of your email?

Bacon

[BonusCup]

@abacon I tried that also.  At the top of post /admin/v1/workflows, it says the "owner parameter is the user's email" but I tried the ownerID also.

[abacon]

@BonusCup So it does, apologies. 

I am just throwing stuff against a wall as I haven't done this but would the option below work instead of the v1 API?

Bacon

[BonusCup · Accepted solution]

UPDATE:  With the help of Alteryx support, I was able to migrate a workflow that was flagged as "Ready to Be Migrated" from our Dev server to our Prod server.  They had me use the "Server API" tool and NOT the "Server V3 API" tool to upload to the Prod server.  

IMPORTANT: 

• The workflow being migrated needs to be on the same version, or earlier version, as the server it is being migrated to.
  • In one of my tests, our dev environment is on 2024.2 and our Prod server is on 2023.1.  I already had a test WF on our Dev server and it would constantly fail to migrate.  I created a WF on our 2023.1 and saved it to the Dev server and it successfully migrated from Dev to Prod.

For our use case, and reason for testing, we will have our designers do all of their development work in the Dev server. Once they are ready for production, they will review their WF with an Admin to ensure all security requirements, documentation, and best practices are in place.  Once approved, the admin will flag the WF as ready to migrate and will trigger another WF to migrate the WF into the user's Prod Studio.