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
- 2.1K All Categories
- 18 General
- 155 Installation / Setup
- 991 Flows
- 86 Rules
- 203 Administration
- 204 Portal
- 433 General Q & A
- 600 Forms
- 282 Reports
- 3 Designer Extensions
- 38 Example Flows
- 32 CSS Examples
- 1 Diagram Tile
- 5 Javascript Controls
- 139 Pages
- 1 Process Mining
- New Features
- 150 Datastructures
- 50 Repository
- 169 Integrations
- 25 Multi-Tenant
- 21 SDK
- 40 Modules
- 38 Settings
- 20 Active Directory
- 12 Version 7
- 34 Version 8