Skip to main content
Cadet | Tier 2
November 14, 2025
Solved

Applying Same Delay Action after each Recorder: Capture

  • November 14, 2025
  • 1 reply
  • 91 views

Is there a way to only set up one delay action that will trigger after each of the actions perform successfully? Thanks!

 

    Best answer by Padmakumar

    Hi ​@aacenas,

     

    You can’t apply a single global delay to all Recorder: Capture steps, but you can make it uniform and maintainable:

     

    - Prefer waits over fixed delays: Use “Wait for object/window exists” (with a timeout) before/after Capture. It’s more reliable than hard sleeps and prevents unnecessary waiting.

    - Centralize the delay value: Store a delay (e.g., DELAY_MS) in a variable or bot parameter so you can change it once and have it apply everywhere.

    - Wrap Capture in a reusable subtask: Create a small bot/subroutine like “CaptureWithDelay” that takes the target (object/window) and performs Capture → conditional Wait/Delay using DELAY_MS. Call it for every capture.

    - Apply a uniform delay via error handler: Put captures inside a Try/Catch and add a Delay in Finally; this guarantees a consistent post-step delay without repeating it in each branch.

    - For existing bots: Replace brittle per-step delays with the reusable wrapper and variable-driven waits; this is the fastest path to consistency without editing every line later.

    1 reply

    Padmakumar
    Premier Pathfinder | Tier 7
    Premier Pathfinder | Tier 7
    November 15, 2025

    Hi ​@aacenas,

     

    You can’t apply a single global delay to all Recorder: Capture steps, but you can make it uniform and maintainable:

     

    - Prefer waits over fixed delays: Use “Wait for object/window exists” (with a timeout) before/after Capture. It’s more reliable than hard sleeps and prevents unnecessary waiting.

    - Centralize the delay value: Store a delay (e.g., DELAY_MS) in a variable or bot parameter so you can change it once and have it apply everywhere.

    - Wrap Capture in a reusable subtask: Create a small bot/subroutine like “CaptureWithDelay” that takes the target (object/window) and performs Capture → conditional Wait/Delay using DELAY_MS. Call it for every capture.

    - Apply a uniform delay via error handler: Put captures inside a Try/Catch and add a Delay in Finally; this guarantees a consistent post-step delay without repeating it in each branch.

    - For existing bots: Replace brittle per-step delays with the reusable wrapper and variable-driven waits; this is the fastest path to consistency without editing every line later.

    Padmakumar