Managing blocked async actions

Because some async actions may cause interrupts due to memory or performance issues, Landmark will automatically block those actions. When to block an action depends on either the default settings of three interrupts for the actions within 12 hours, or settings specified in the tenant environment data area for the frequency and timeframe in the blocklist_count and blocklist_timeframe configuration parameters in the async category. For more information, see Runtime Parameters in the ConfigurationParameter Table.

Once and action is blocked it will not be allowed to run until the block is removed.

When an action is blocked the user will be notified via the normal mechanisms:

• If they have elected to be notified for failures or completions and failures, they will get both a user notification and an email (if the actor has an email address set).
• If email addresses were entered on the request, these will also get the message.
• The Async admin receives all failures, including those related to blocking.

To view blocked actions, use the Blocked Actions tab on the Async Administrator Async Overview form or the Blocked Actions list in the Async Framework Components. This will show any blocked actions including how many times it was blocked and the timeframe it occurred within.

On the Blocked Actions tab and list, you can manually add a block or delete a block. If you delete a block that was auto-created by the system, then a confirmation message appears advising that if the underlying issue has not been resolved, the block is likely to be reimposed.