Skip to main content
March 25, 2024
Question

Requirement to have a task alive for more than a year

  • March 25, 2024
  • 5 replies
  • 0 views

We have a request to keep a task open for longer period of time say 6month - 1 year , what are the best practices we need to follow for this case , suppose subprocess run with MNI and creates 100+ task and each should be alive for more than  6 months to one year , please advise what are the best practices we can follow ? 

    5 replies

    venkatrea696188
    March 25, 2024

    Can we know Why you want to keep the task for that long period??  If it comes to me i don't suggest keeping a task for this long. I would go for alternatives like handling things from database (It's against Basic concept of BPM) but i will go for this. Short lived processes

    varuntejg243705
    March 25, 2024

    Hi [mention:4c0976cc949643b68c23e4a0952c6f79:e9ed411860ed4f2ba0265705b8793d05] ,

    The generation of tasks & moreover keeping those active till 1 year is not really a best practice.

    It is not recommended to keep a task active for such long time as it will affect the appian system and its performance.

    Appian always recommends to only use short-lived processes.

    Server health & maintenance is a big concern, when you get around these long running processes.

    Instead deal with record-centric approach, it helps to trigger the action anytime.(Suggestion)

    I hope, this clears you.

    stefanhelzle0001
    March 25, 2024

    I covered that in a blog post. Find it here: https://appian.rocks/2023/03/20/design-long-running-tasks/

    March 25, 2024

    Thanks Stefan for your recommended solutions 

    shubhama926776
    March 31, 2024

    Database-driven approach would be better choice to achieve this.
    Storing tasks involves leveraging relational database tables to store task-related data. This approach provides scalability, flexibility, and performance benefits compared to storing tasks directly within the Appian platform.