Make that, Postponed. The status for over a hundred results were marked Postponed.
We’re using v2.0 of the platform. After manually restarting the jobs, we were able to get the documents converted from Word to PDF.
But now we are having a different issue. The document conversions are displayed as “Completed” on our GroupDocs’ dashboard, but when we tried to pull them down to our S3 bucket we believe the API is refusing to retrieve our completed jobs.
Here are the operations we are running: 1)
upload_file_to_groupdocs to put our copy of the file onto GroupDocs server, 2)
start_groupdocs_file_conversion to convert that uploaded file, and 3)
retrieve_groupdocs_render to save the resultant file to S3 and save the path to our db so we can access it later.
At first, some of the
retrieve_groupdocs_render tasks were aborting after 10 retries because the status was either “Scheduled”, “Pending”, or even worse, “Postponed”.
For the “Postponed” jobs, we manually restarted them from the Dashboard. One by one.
Then we stripped the arguments out of the logs and repeated the
retrieve_groupdocs_render tasks. The latest issue was that
start_groupdocs_file_conversion was not returning a job uid, which we assume means the service was not accepting our job.
FYI, we may be approaching our limit of 750 operations per month, but our understanding was that each additional operation would cost $0.15, so there should be no reason that the operations would get cut off because we ran over our limit.
Please let us know how we should proceed to retrieve the remaining jobs.
We haven’t, and may, but how does that relate to document conversions? We didn’t have any trouble uploading documents to GroupDocs. We had trouble with conversion jobs; over a hundred were stuck in a Postponed state. Why did that happen?