Launch a Wrkflow: Wrkflow UUID not found

Leeann

Hi @Product

Occasionally, the Launch a Wrkflow WA will return the error that the UUID was not found, but it exists and on reset its fine.

Launch ID: 1086539
Launch Name: User:210949|ReqID:1387523
Wrkflow Name: Nursys & CNA/GNA Launcher
Wrkflow Version: 51807
Execution ID: 1235dd8e-f5d8-4d9e-baa7-c201190ecdad

Successful reset: Execution ID: 2cb6d480-338f-4de4-9410-d7920cc8d9c5

Dylan

Leeann Thanks for flagging this and for sharing the details. I’ve looked into it, and it seems to be a temporary hiccup where the system briefly thinks the workflow doesn’t exist, even though it does. That’s why a reset usually fixes it right away.

I’ve logged a ticket for this so we can handle it more gracefully going forward by automatically retrying instead of failing.
https://wrk-technologies.atlassian.net/browse/SUP-1718

Dylan

Leeann After some further review, it looks like we won’t be able to simply mask this error and retry, since the error is the same one returned when an invalid UUID is used while launching a Wrkflow.

The correct path forward is to move this flow over to the Platform API Wrk Actions( Launch a Sync Wrkflow or Launch an Async Wrkflow), which provide better support and more reliable error reporting than the legacy API.

That said, the Platform API Actions do not currently support files. If this Wrkflow relies on file inputs, it may not be possible to migrate at this time.