0

I am getting a 404 failedUpload error.

My activity and work item are all consistent with local names, and are created correctly and working.

My bucket exists and I can upload files to it and delete them. Token is correct

The plugin works locally and outputs the output.json with the expected data and the plugin_log.txt.

I am logging the contents of the working folder, and all the files are there

Command: (command "EXTRACTLAYERS")
[02/22/2025 01:10:12] EXTRACTLAYERS
[02/22/2025 01:10:16] Working folder: C:\DARoot\Jobs\b3f8456b813c44c7963e09d5285e5bf0
[02/22/2025 01:10:33] Output file should now be present at: C:\DARoot\Jobs\b3f8456b813c44c7963e09d5285e5bf0\output.json
[02/22/2025 01:10:33] Final working folder contents:
[02/22/2025 01:10:33] - b3f8456b813c44c7963e09d5285e5bf0.log (4172 bytes)
[02/22/2025 01:10:33] - b3f8456b813c44c7963e09d5285e5bf0_Job.das (1340 bytes)
[02/22/2025 01:10:33] - input.dwg (30369815 bytes)
[02/22/2025 01:10:33] - output.json (78187 bytes)
[02/22/2025 01:10:33] - plugin_log.txt (3197 bytes)
[02/22/2025 01:10:33] - setting_script.scr (29 bytes)

Then this happens

End script phase.
[02/22/2025 01:10:34] Start upload phase.
[02/22/2025 01:10:34] Uploading 'C:\DARoot\Jobs\b3f8456b813c44c7963e09d5285e5bf0\output.json': verb - 'Put', url - 'https://developer.api.autodesk.com/oss/v2/buckets/aps_bucket/objects/output.json/signeds3upload'
[02/22/2025 01:10:34] Uploading 'C:\DARoot\Jobs\b3f8456b813c44c7963e09d5285e5bf0\plugin_log.txt': verb - 'Put', url - 'https://developer.api.autodesk.com/oss/v2/buckets/aps_bucket/objects/plugin_log.txt/signeds3upload'
[02/22/2025 01:10:35] Error: Failed - 404 (Not Found)

I have tried delays in the plugin to see if it was a timing issue. but get the same results or if it is too much of a delay it doesn’t run correctly and throws a failedInstructions error.

Anyone experience this issue before?

I am uploading a dwg to the APS DA API, and I expect to receive a json file or data back. The file size should not be more that I would assume 500KB or at the highest a MB. Locally this operation is about 30 seconds.

1 Answer 1

0

An HTTP 404 error means that the URL you provided does not exist for the given HTTP verb - in your case PUT. /buckets/:bucketKey/objects/:objectKey/signeds3upload endpoint is a POST or GET operation, not PUT, but even if you provided POST or GET, I don't think it would work here like that.

Just like you created a pre-signed URL (usually looks like https://cdn.us.oss.api.autodesk.com/oss/v2/signedresources/...) for the input, you should do the same for the outputs.

Or you could use this new solution where you can simply pass the URN of the files and provide the access token:
https://aps.autodesk.com/blog/new-feature-support-direct-s3-migration-inputoutput-files-design-automation

Sign up to request clarification or add additional context in comments.

3 Comments

I have now go this workitem being successful but now get this error. 'Current WorkItem status: success ✅ WorkItem completed successfully. Fetching Autodesk Forge token... Reusing existing token. ❌ Error generating signed download URL for output: { developerMessage: 'The requested resource does not exist.', moreInfo: 'aps.autodesk.com/en/docs/oauth/v2/developers_guide/…', errorCode: '' }'
Where are you getting that error? The work item status can only be "success" if both input/output downloads/uploads succeeded. Can you provide the full work item report?
I have resolved that error. But I am still not able to get the file data or download it. If I try getting it with a token it throws an error for not being authorized. Just using the object ID is not working. And I am not getting any logs through APS only terminal error logs. No report.txt. But I’m going to try a few things. I will email them through that email thread.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.