Server Workflow - The Ticket is Not Valid?

Sean McClurkan

31. Juli 2019 19:40

My server workflow is throwing an error about "The ticket is not valid". The workflow item is shared with Everyone in AGOL. What else do I need to do to run the workflow?

0

• 

  Stefan Schweigert

  31. Juli 2019 20:13

  Hi Sean,

   

  I have few questions to start.

   

  1. Have you specified within the Info panel that this is a server workflow, and contains no warnings about client activities being present?
  2. Are you executing the server workflow by using a client workflow that references the server workflow and passing parameters?
  3. Are you able to run other server workflows?
  4. What version of GXWF on-prem, your OS, and browser are you using?

   

  Thanks, Stefan

  0
• 

  Sean McClurkan

  31. Juli 2019 20:19

  1. Have you specified within the Info panel that this is a server workflow, and contains no warnings about client activities being present? Yes. Info Panel shows Server Workflow with no errors or warnings 1. Are you executing the server workflow by using a client workflow that references the server workflow and passing parameters? Yes 1. Are you able to run other server workflows? Yes 1. What version of GXWF on-prem, your OS, and browser are you using? GW5 5.11.0 On-Premise Windows 10 64-bit Chrome

  0
• 

  Stefan Schweigert

  31. Juli 2019 22:37

  Hi Sean,

   

  That error indicates that the workflow attempted to run but failed.

   

  1. Do any activities run or does the workflow fail to run initially?
  2. Any additional error information in the browser console (F12)?
  3. Are you able to share the workflow .json file?

   

  On a side note, we support installing on-prem only on Windows Server versions.

   

  Stefan

  0
• 

  Sean McClurkan

  31. Juli 2019 23:02

  Sorry. Our Workflow server is Windows Server 2012 R2. The workflow fails immediately on launch. I got this error message about the ticket from a link in the console: { "error": { "id": "GW001.400", "message": "GW001.400: Bad Request", "status": 400 }, "log": { "start": "2019-07-31T22:58:36.3531575Z", "end": "2019-07-31T22:58:36.3543426Z", "artifacts": [ { "$type": "PortalChallenge", "id": "72e25069065e4d7f984b9b2d36e0f47b", "portalUrl": "https://austin.maps.arcgis.com/" }, { "$type": "JobTokenError", "id": "f2535d21e0784826b9c890eb5851fa3d" } ], "traces": [ "Information: 0: Logs: http://www.austintexas.gov/Geocortex/Workflow/service/job/logs?ticket=eyJhbGciOiJub25lIiwiemlwIjoiREVGIn0.q1ZKzs9TsqpWUimpLEhVslLyKi8JyUzOTi1xzs8rSc0rUdJRyspP8kwBShnoG5pbJhsmJlqYm5qYmSSZGCdZJJqbpqUkJluYm1kmppoo1dYCAA", "Error: 0: Access scope not valid: 72e25069065e4d7f984b9b2d36e0f47b", "Error: 0: The ticket is not valid: f2535d21e0784826b9c890eb5851fa3d" ] } } The workflow is on AGOL at: https://austin.maps.arcgis.com/home/item.html?id=5aa7efb8a4ca40efa12e2231daa08ff1 It takes two Input Parameters: arFolderRSN and arFolderType

  0
• 

  Stefan Schweigert

  1. August 2019 20:11

  Hi Sean,

   

  I opened your workflow and it appears that the Run Workflow activity is referencing the current workflow, creating an infinite loop. Could you take a look?

   

  Thanks, Stefan

  0
• 

  Sean McClurkan

  1. August 2019 21:37

  Thanks, Stefan. I think it was, plus a few other oddities that my co-worker, Lee Kinser, was able to identify. Once we worked through logging steps out of the server side workflow, we were able to get it working. Thanks again for the quick response. Now if you could sort out why some of my Query Task results are bufferable and some aren’t I’ll be in high cotton . . .

  0
• 

  Stefan Schweigert

  1. August 2019 23:01

  No problem!

   

  Take a look at this section of the online docs: https://docs.geocortex.com/workflow/latest/help/Default.htm#wf5/help/geometries.htm#Buffer_a_Geometry%3FTocPath%3DModels%7CWork%2520with%2520Geometries%7C_____4 which might have some useful information.

   

   

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.