Get a configuration workflow run's full detail
Gets one run's full detail, including the full discovered payload behind its summary counts - fetched on demand (not part of the paginated run list, which stays lean) since a heavily-discovered run's payload can be sizeable.
Path parameters
Response
The run, with its full discovered payload
Example response
{
"triggerType": "manual",
"status": "COMPLETED",
"triggeredBy": {
"id": "abc123",
"friendlyName": "John Doe (john.doe)"
},
"entries": [
{
"status": "new"
}
]
}Changes
Changed in 5 of the 241 revisions of this API.23
- ○
endpoint added
endpoint-added
This revision also has 25 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 113 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
endpoint added
endpoint-added
This revision also has 31 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 96 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
endpoint added
endpoint-added
- ○