Plaza 365
Plaza 365

No results found for your search

RegisterLog in

5

Visit article

#report

Dynamics 365 ERP - Development

Category

Feb 22, 2025

Published date

Text

Article Type


AI Summary

  • The article discusses a long-running report in SaaS that calculates profitability and the challenges faced with hitting operational limits, leading to report timeouts.
  • The report was divided into 7 distinct processes to overcome operational limits and allow for more time per process.
  • A Job Queue was created at the end of each process to spawn the subsequent one, ensuring persistent intermediate values and the ability to continue from a failed step.
  • Despite optimizations, the longest step continued to run into a timeout after 12 hours, prompting the need to elevate the job timeout to 24 hours.
  • The overall process took approximately 41 hours to complete, highlighting the complexity and challenges faced in handling such stretched scenarios.
  • The key takeaways include decoupling monolithic processes, saving states to avoid lengthy rollbacks, and adjusting timeouts to accommodate for extended processing times in SaaS environments.
  • Instrumenting each process with telemetry signals and being aware of operational limits in SaaS are crucial for efficient and successful execution.
  • Despite the challenges faced, the article concludes that breaking down processes, saving states, and adjusting timeouts can lead to successful outcomes even in complex scenarios.

Registered users can view the full text for FREE!

Sign In Now!