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.5K All Categories
- 86 General
- 13 Training
- 213 Installation / Setup
- 1.2K Flows
- 112 Rules
- 277 Administration
- 215 Portal
- 503 General Q & A
- 722 Forms
- 356 Reports
- 3 Designer Extensions
- 47 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 8 Javascript Controls
- 189 Pages
- 5 Process Mining
- New Features
- 187 Datastructures
- 72 Repository
- 237 Integrations
- 30 Multi-Tenant
- 27 SDK
- 81 Modules
- 60 Settings
- 26 Active Directory
- 12 Version 7
- 37 Version 8
- 143 Lunch And Learn Questions