Flow Only Returning the Tracking ID?
Comments
-
Im calling a flow as a service and Im only getting a tracking ID back despite the flow having clearly defined outputs. The flow has a couple subflows within in, but its otherwise just a standard flow. Why is it doing this?
-
Hello Jon,\r\n\r\nI'm guessing that these subflows are probably async and/or have assignments, state changes, or certain other components that could put the flow into a \"stored state\". Anything that causes a workflow to go into a stored state will cause the service to return a flow tracking ID.\r\n\r\nIt does this so that the sender does not have to sit and wait for a response from a flow that could potentially sit for a long period of time.\r\n\r\nYou can use these IDs to get the results of the flow after it's complete. One solution you could use would be to store these IDs into a \"queue\
Howdy, Stranger!
Categories
- 4.4K All Categories
- 80 General
- 13 Training
- 209 Installation / Setup
- 1.1K Flows
- 110 Rules
- 270 Administration
- 213 Portal
- 497 General Q & A
- 709 Forms
- 345 Reports
- 3 Designer Extensions
- 48 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 186 Pages
- 5 Process Mining
- New Features
- 186 Datastructures
- 70 Repository
- 229 Integrations
- 29 Multi-Tenant
- 27 SDK
- 81 Modules
- 59 Settings
- 26 Active Directory
- 12 Version 7
- 35 Version 8
- 143 Lunch And Learn Questions