Aspose Cells Cloud 24.1.0 – Intermittent Evaluation Tab Despite Valid License

The Aspose-cell service intermittently fails during report generation. Although reports are successfully delivered, an unexpected “Evaluation” tab appears within them, leading to confusion and a negative user experience.

Environment Details

  • Image: aspose/cells-cloud:linux.24.1.0
  • Deployment: Single ECS container (8GB RAM / 4 vCPUs)
  • Hosting: AWS ECS (Fargate)

Behavior Observed

  • The resulting Excel files include an additional “Evaluation” tab, despite valid licensing.
  • No errors or warnings appear in ECS logs — the container logs show no relevant output during the incidents.
  • Resource metrics (CPU, memory, and I/O) show no saturation or performance degradation at the time of failure.
  • The issue is fixed after re-reploying the ECS service/container.

@mbaltodano

It appears you are encountering an issue with the Aspose.Cells Cloud service, where an unexpected “Evaluation” tab is appearing in your generated reports, despite having a valid license. This can be frustrating, especially when there are no errors or warnings in the logs.

Here are several steps you can take to troubleshoot and potentially resolve this issue:

  1. License Application: Verify that the license is being applied correctly in your application. The license should be loaded once per application lifecycle before any operations are performed. If the license is not applied correctly, the service may revert to evaluation mode.

  2. Container Deployment: Since you mentioned that the issue resolves after redeploying the ECS service/container, consider implementing a health check or a restart policy for your container. This may help in automatically recovering from intermittent issues.

  3. Logs and Monitoring: Although you noted that there are no relevant outputs in the logs, consider enhancing your logging to capture more detailed information about the application’s state when the issue occurs. This could include logging the license status or any exceptions that might not be surfacing.

  4. Version Check: Ensure that you are using the latest version of the Aspose.Cells Cloud SDK. Bugs are sometimes fixed in newer releases, so updating may resolve the issue.

  5. Contact Support: If the problem persists, consider reaching out to Aspose support with detailed information about your environment and the issue. They may have insights or fixes for this specific problem.

If you continue to face challenges, reviewing the licensing documentation for Aspose.Cells may provide additional insights into proper license management.

Feel free to ask if you have any further questions!

Those steps have already been taken (the ones applicable to our setup):

  1. The service is running in Docker; it’s not a metered service.
  2. That step would not prevent the issue from occurring.
  3. Logs are limited in the Docker version, and the minimal information provided by the image does not help in determining the root cause.
  4. We have already reviewed the release notes — it’s possible the issue was addressed at some point, but it’s not clearly documented.
  5. We would definitely like to obtain support.