Preventing Scheduled Process Models from kicking off multiple instances after system downtime?

Certified Senior Developer
Does anyone have any recommended approaches to preventing a process model that runs on a recurring schedule from kicking off multiple instances after the system is down when it was scheduled to run? We have some processes that run nightly, but can create race-conditions if multiple instances try to run simultaneously.

Thinking about maybe putting in an "Advanced Options" Expression to force it to actually be the scheduled start time (or at least close), and just bypassing running until the next scheduled time that Appian is actually up on the server. Would that do the trick?

OriginalPostID-254265

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer
    Christine - The constant method is out. We used this in a couple places, and ended up with major issues in production with our collaboration engine completely out of control (it grew to 42 GB as the constant amassed 55,000 versions). We had to delete the constant and re-import it as a temporary fix to the memory leak, but we're moving away from using the "Update Constant" smart service and using this pattern.
Reply
  • 0
    Certified Senior Developer
    Christine - The constant method is out. We used this in a couple places, and ended up with major issues in production with our collaboration engine completely out of control (it grew to 42 GB as the constant amassed 55,000 versions). We had to delete the constant and re-import it as a temporary fix to the memory leak, but we're moving away from using the "Update Constant" smart service and using this pattern.
Children
No Data