Recalculate project endpoint return 504 gateway timeout error

Hey there,

we currently get 504 Gateway timeout errors for some customer exports that involve recalculate project API calls. Those endpoint calls also don’t show up in the API usage logs.
One of the failed calls is the following: https://api.aspose.cloud/v3.0/tasks/5490960a-9dd7-47f4-85a8-bba23e57e93e.xml/recalculate/project

This is currently impacting our production customers so help would be greatly appreciated.

Best regards
Lasse

@lasse.steffen

It seems that you are experiencing 504 Gateway timeout errors when making API calls to the Recalculate Project endpoint. This issue has been reported by other users as well, indicating that it may not be isolated to your implementation.

Here are some steps you can take to mitigate the issue:

  1. Implement a Backoff Strategy: Similar to other users, consider implementing a backoff strategy for your API calls. This involves retrying the request after a delay, which can help in cases where the server is temporarily overloaded. For example, you could start with a 5-second wait and double the wait time with each subsequent retry (e.g., 5, 10, 20, 40 seconds).

  2. Monitor API Usage: Since you mentioned that the failed calls do not appear in the API usage logs, it might be beneficial to monitor your API usage closely. This can help identify patterns or specific conditions under which the timeouts occur.

  3. Contact Support: Given that this issue is impacting your production environment, it may be helpful to reach out to Aspose support directly. They are aware of similar issues and are actively working on resolving them. Keeping them informed about your specific case could expedite a solution.

  4. Check for Updates: Regularly check the Aspose forums or your support ticket for updates regarding the status of the issue. Other users have reported similar experiences, and the support team is working on a fix.

If you continue to face issues, please provide any additional details about your implementation or specific scenarios where the timeouts occur, as this information can assist in troubleshooting.

Sources:
[1]: Tasks 504 Gateway Time-out / 502 Bad Gateway

The issue is reproducible for a specific customer and project so a backoff strategy doesn’t fix our issue when it happens on every request.

Is it possible to have someone from the support team look at this?

@lasse.steffen ,

Is the request always failing for the specific customer and project?

It’s always reproducible for the customer and project.

@lasse.steffen ,
can you attach the project file?

We can’t share confidential customer data with you. Are you able to access any logs via the provided endpoint URL above?

@lasse.steffen ,
ok, we will try to investigate without the project file.