Workfront Fusion

Ken_Qrious · 3/2/25

Based on the documentation at https://developers.make.com/api-documentation/api-reference/scenarios/logs/get--scenarios--scenarioi... the following api call should do the trick. The api call works but the response is not what is expected. The response I am getting looks more like a scenario change audit.

Documentation

API Request (Get)

https://eu1.make.com/api/v2/scenarios/{scenarioId}/logs

API Response

{

"scenarioLogs": [

"pg": {

"sortBy": "imtId",

"sortDir": "desc",

"last": "1632371803593_scenario.1229.auto.3cf2f332f74f43f1b2c4ae431cbedb5b",

"showLast": false,

"limit": 50

},

{

"imtId": "1632371744497_scenario.1229.auto.da518adcd14b4b64ac6358823ccb80ca",

"duration": 19979,

"operations": 10,

"transfer": 3942,

"organizationId": 21,

"teamId": 27,

"id": "da518adcd14b4b64ac6358823ccb80ca",

"type": "auto",

"authorId": null,

"instant": false,

"timestamp": "2021-09-23T04:35:44.497Z",

"status": 1

}

]

}

Actual (with sensitive data substituted)

API Request (Get)

https://app.workfrontfusion.com/api/v2/scenarios/123456/logs

API Response

{

"scenarioLogs": [

{

"imtId": "1111111111111_222222",

"id": "222222",

"executionId": "222222",

"detail": {

"author": {

"name": "Jo Developer",

"staff": false

}

},

"type": "modify",

"authorId": 12121,

"timestamp": "2025-02-25T21:08:05.605Z"

},

{

"imtId": "3333333333333_444444",

"id": "444444",

"executionId": "444444",

"detail": {

"author": {

"name": "Jo Developer",

"staff": false

}

},

"type": "start",

"authorId": 12121,

"timestamp": "2025-02-25T21:08:02.872Z"

}

],

"pg": {

"sortBy": "imtId",

"limit": 50,

"sortDir": "desc",

"offset": 0

}

lgaertner · 3/3/25

Hello Ken,

the question is, what returned information you are expecting?

As you can see here, you get detailed information on an execution, if you are extending your API call with an execution ID.

/scenarios/{scenarioId}/logs/{executionId}

The documentation of make.com mentions, that you need to use
The unique ID of the scenario execution. It can be retrieved from the List scenario logs endpoint under the ID key.

As your response already includes a key called executionId, that could be the required id.

Regards

Lars

Ken_Qrious · 3/3/25

Hello Lars,

What I'm expecting is a valid execution id so that I can retrieve the execution details with /scenarios/{scenarioId}/logs/{executionId}. In the documentation example the execution id is a longer value ("id": "da518adcd14b4b64ac6358823ccb80ca"). If I grab the actual execution id from fusion the /scenarios/{scenarioId}/logs/{executionId} works fine. Wh I am getting is a shorter value ("executionId": "222222"). If I try to use the execution id that returned (/scenarios//123456/logs/222222) I get the following error

{

"detail": "Validation failed for 1 parameter(s).",

"message": "Bad Request",

"code": "SC400",

"suberrors": [

{

"message": "Value doesn't match pattern in parameter 'executionId'.",

"name": "Error"

}

]

}

Sven-iX · 3/3/25

Hi @Ken_Qrious

Looks like Adobe modified this part of the API and we're out of luck:

When I make the request to /api/v2/scenarios/123456/logs like you did - it only returns the last Save points of the scenario, no executions.

Looking at the front-end, I see that the actual call retrieving executions is

/api/v1/logs/scenario/23701?orderby=-timestamp&limit=50

That call doesn't like the API tokens (denied) and when you paste in the Bearer Token from DevTools I get "Forbidden resource"

So it seems the walled that off. Go ahead and enter a ticket. I'm doing the same.

ArunNa3 · 3/3/25

Hello @Sven-iX @Ken_Qrious :: I am also facing the same issue. Just thought of checking if you guys got any fix for this problem. My jobs were running fine until last week and started breaking from today on due this problem

Sven-iX · 3/3/25

Please raise a ticket and complain. Especially if you had jobs using this API call.

Appalling they just jank this.

Sven-iX · 3/4/25

@Ken_Qrious @ArunNa3 @lgaertner

update from support

Unfortunately, our Fusion API is a part of our unsupported API. Which means while it can be used, it is not something that we will investigate or troubleshoot should it not behave as expected. There may have been updates or changes to this but based on my teams response, I am sorry to say there is not any workaround solution we can currently offer for this.

I would suggest putting this in a feature request to support our Fusion API or to enable this in some capacity, additionally you could also reach out to our Workfront/Fusion consultants and see if they have any custom solutions for this in place that they could share. I'm not finding anything on my end internally or on Experience League that will provide this solution today.