A few generic troubleshooting tips that may help you troubleshoot with Asset Compute Service are:
Ensure that all dependencies to be installed are referenced in the application’s
Ensure any errors that may come from cleanup on failure don’t generate their own errors that hide the original problem.
When starting the developer tool for the first time with a new Asset Compute Service integration, it may fail the first processing request because the Asset Compute Events Journal may not be completely set up. Wait for some time for the journal to set up before sending another request.
If you run into errors sending Asset Compute
/process requests, make sure that all the necessary APIs are added to the Adobe I/O Project and Workspace—that is, Asset Compute, Adobe I/O Events, Adobe I/O Events Management, and Adobe I/O Runtime.
If you have issues logging in to the Adobe Developer Console through the Adobe I/O CLI, then manually add the credentials required for developing, testing, and deploying your custom application:
Navigate to your Firefly project and workspace on the Adobe Developer Console and press Download from the top-right corner. Open this file and save this JSON to a safe place on your machine.
Navigate to the ENV file in your Firefly Application.
Add the Adobe I/O Runtime Credentials. Get the Adobe I/O A Runtime credentials from the downloaded JSON. The credentials are under
project.workspace.services.runtime. Add the Adobe I/O Runtime credentials in the
Add the absolute path to the downloaded JSON in Step 1:
Set up the rest of the required credentials needed for the developer tool.