Aspose Cells Cloud 24.1.0 – Intermittent Evaluation Tab Despite Valid License

Aspose.Cells Cloud Product Family
1

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.
2

@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!

3

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.
4

@mbaltodano Hello, we have received feedback and are investigating the cause.

5

@mbaltodano Hello, this issue may be caused by a misconfigured license. How did you configure the license? Are you using metered billing mode or license billing mode?

Also, I’d like to ask what symptoms occur when this issue occurs so we can simulate and resolve it.

6

If I am not mistaken: License billing mode, because we have SubscriptionApiKeys. The issue is not related to a misconfigured license because the issue disappears when a the ECS containers are restarted. We have not observed symptoms, the reports are generated but they include the evaluation tab, from the metrics/monitoring perspective the ECS instance is ok (almost not being used [Low memory and Low CPU])

7

@mbaltodano Thank you for your reply, we will continue to investigate the cause of this issue.

8

@mbaltodano Hello, metered billing mode requires an internet connection. I’d like to ask about your network status. When the evaluation page appears, is the network connection normal? If convenient, you can try the latest version.

9

I just realized the billing mode is metered (The invoice says Metered item ‘Credits’ usage …"). Network was normal while the issue occurred. In fact the only thing that changes the behavior of adding the evaluation tab on the reports it is a service restart (it does not solve by itself). I have attached some metrics
aspose-network-tx.png (48.5 KB)

aspose-network-rx.png (40.2 KB)

aspose-cpu.png (41.3 KB)

aspose-memory.png (52.5 KB)

The Aspose-Cell service runs on a single ECS instance, and it is accessed through a Load Balancer, which hasn’t shown any abnormal behavior. I’ll discuss with the team whether we can upgrade the service version.

However, this issue is quite unusual for us, as we have 6–8 licenses distributed across different environments and regions, all with the exact same setup (created using IaC tools). The problem occurs only in this setup. Our assumption is that the service might stop working properly due to high usage — since the affected environment is the most heavily used compared to the others — and then start acting up again. However, as mentioned earlier, there’s nothing concrete; the metrics look fine.

10

We have received feedback and will continue to investigate the cause.