Skip to main content

Manage Scheduled Execute Cards

Quick Setup

Most teams set up or update one card in about 5 minutes.

Use this guide when you want one block to run another block later. It also explains why edits and deletes now use a stable schedule identity. Labels with underscores stay intact.

Go to: Bot Builder → Cards → Scheduled Execute

Quick Reference​

SettingWhat it controlsWhat to check
Schedule NameThe label you see in the editorUse a unique name for each schedule
Date TypeExact, relative, or repeating timingMatch the timing you actually need
Execute BlockThe block that runs laterChoose the correct target block
IdentityHidden key AVA uses for saves and deletesKeep the same card open when editing
SaveStores the card and identitySave after every edit

Before You Start​

Confirm these items:

  • You can edit Bot Builder cards
  • The target block already exists
  • You know whether the schedule is one-time or repeating
  • You want a unique Schedule Name for each scheduled action
Stable identity

AVA now keeps a hidden identity for each Scheduled Execute card. You still see the display name in the editor. If you reopen an older card, AVA restores the same identity when it can.

Create Or Edit A Card​

  1. Open the bot collection that contains the card.

  2. Click Add Scheduled Execute Block.

  3. Choose Exact Date, Relative Date, or Repeating Date.

  4. Enter the schedule details shown on the card.

  5. Fill in Schedule Name.

  6. Choose the Execute Block that should run.

  7. Click Save.

    ✓ The card stays in the list after save. ✓ AVA assigns or keeps the stable schedule identity.

Why this matters

Identity keeps the schedule tied to the same card after edits. That reduces duplicate runs. AVA also keeps the visible label separate from the internal identity. That lets you rename the card without changing the schedule.

Delete A Card​

  1. Open the Scheduled Execute card you want to remove.

  2. Click Remove Card.

  3. If the card has no stored identity, AVA matches by label only when the match is unique.

  4. If AVA shows a duplicate-name warning, rename one of the cards first.

  5. Save the renamed card.

  6. Try Remove Card again.

    ✓ AVA deletes the tracked schedule for that identity. ✓ It does not guess based on a shared label.

Troubleshooting​

Delete Says The Label Is Ambiguous​

What you see: AVA says the Scheduled Execute label is ambiguous.

Fix:

  1. Open the matching cards.
  2. Give each one a unique Schedule Name.
  3. Save the cards.
  4. Retry Remove Card on the correct one.
Legacy delete cards

Older delete cards can only resolve by label when one matching Scheduled Execute card exists. If more than one card matches, AVA stops the save and asks you to disambiguate.

An Old Schedule Still Appears Active​

What you see: You edited a card, but the previous run still exists.

Fix:

  1. Confirm the card was saved successfully.
  2. Reopen the card and check the updated timing.
  3. If the card was created outside the editor, open it here and save it once.
  4. If the problem continues, check for a duplicate card with the same name.

A Card Name With Underscores Looks Wrong​

What you see: The editor shows a label with underscores, but the schedule looks different.

Fix:

  1. Use the display name you want in Schedule Name.
  2. Save the card again.
  3. Remember that AVA reads the label from the first underscore onward.
  4. Do not use the label as the only way to identify the schedule.
What AVA stores

AVA keeps the display label separate from the internal identity. That lets you use readable labels without changing the tracked schedule. It also keeps text after the first underscore in the visible label.

Still Stuck?​

Contact success@vouch-technologies.com if:

  • ❌ Remove Card still fails after you make the name unique
  • ❌ A saved card does not keep its timing
  • ❌ You see an error after editing or deleting the card

Helpful to include:

  • The bot collection name
  • The schedule name
  • A screenshot of the warning
  • The steps you already tried