Hello
I have a scenario connected to a Soundcloud account that works fine. However, on another account, I can’t figure why but I can’t post an episode
Here is the input
[
{
“genre”: “technology”,
“title”: “Elon Musk et l’avenir de l’IA : Open Source et Collaboration avec Grok”,
“asset_data”: “IMTBuffer(2329150, binary, e8b2ea6dc5b775959dd7dbc0ae8bd4863734393b): 4944330300000000047e5449543200000039000001fffe4600720020004600720020006f00700065006e0061006900200074007400730020006f007500740070007500740020006d007000330054414c4200000045000001fffe41004900200069006e00”,
“streamable”: true,
“commentable”: false,
“artwork_data”: “output1.png”,
“downloadable”: true
}
]
And Output
[
null
]
Is there any error message? Also
If you have the Make DevTool Chrome extension installed, you should be able to view the request and response headers and body from each module when you manually run the scenario.
From the Help Center article about the Make DevTool:
Make DevTool allows you to debug your Make scenarios in a completely new way. It adds an extra pane to the Chrome Developer Tools. Using this new debugger pane, you’re able to check all the manual runs of your scenario, review all the performed operations and see the details of every API call performed. It also brings a whole bunch of new opportunities for Apps development. You’re able to check every call that your app has performed. Thanks to this extension, you can easily debug your scenario, see which module, operation, even which single response causes the error, and then get your scenario back on track. Try it out and let your scenarios shine!
For more information on how to install and use this, see https://www.make.com/en/help/scenarios/integromat-devtool
2 Likes
Thanks here is what I get
{
“content-type”: “text/plain; charset=utf-8”,
“content-length”: “0”,
“connection”: “close”,
“date”: “Tue, 19 Mar 2024 01:47:53 GMT”,
“strict-transport-security”: “max-age=63072000; includeSubdomains; preload”,
“server”: “am/2”,
“x-cache”: “Error from cloudfront”,
“via”: “1.1 5beb4c3232a40c8c6a3e48c902092760.cloudfront.net (CloudFront)”,
“x-amz-cf-pop”: “IAD89-C2”,
“x-amz-cf-id”: “2RlfE_eUusyCmvodOs-sEh0mnAiIYe8ooVMLEsWc58GLXvHlI3Uqfw==”
}
Looks like this is an unrelated issue, from the file hosting company that SoundCloud is using.
I would suggest contacting SoundCloud for more information.
2 Likes
Thanks I will keep you posted.