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

Setting	What it controls	What to check
Schedule Name	The label you see in the editor	Use a unique name for each schedule
Date Type	Exact, relative, or repeating timing	Match the timing you actually need
Execute Block	The block that runs later	Choose the correct target block
Identity	Hidden key AVA uses for saves and deletes	Keep the same card open when editing
Save	Stores the card and identity	Save 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.

Understand Scheduled Report Retries

AVA can retry a scheduled report when its runtime returns a structured fallback. Normal answers with partial property failures do not start this retry flow.

What happens	What you can expect
Original execution	AVA runs the scheduled report once.
Retry attempts	AVA can make up to three additional attempts.
Retry timing	Retries are queued after about 30, 60, and 120 seconds.
Retry window	AVA stops retries after ten minutes.
Regular schedule	Your next recurring run remains independent.

Read-only scheduled reports

Retries preserve the original prompt, agent, reporting time, and property access. They do not include group history, compact memory, or quoted replies.

Read Retry Details In Activity

1. Open Settings → Communications → Chatbot.

2. Open the agent's Activity tab.

3. Find the scheduled report by its schedule name.

4. Check the attempt label, intended time, and retry state.

5. Check Execution and Delivery separately.

   ✓ Original attempt identifies the first run. ✓ Retry 1/3, Retry 2/3, or Retry 3/3 identifies a retry. ✓ Scheduled for shows the intended reporting time. ✓ Next retry appears when AVA has queued another attempt. ✓ Execution shows an answer, proposal, fallback, or pending result. ✓ Delivery shows whether AVA sent the resulting report.

The Activity row can show Retry queued, Completed, Retry publication failed, Retries exhausted, or Retry stopped. Each destination group has its own retry chain.

Activity detail	What it means
Schedule name	The scheduled report linked to the attempt
Scheduled for	The report time the original schedule intended
Original attempt	The first execution for this report
Retry 1/3 to Retry 3/3	A later fallback retry
Execution	What AVA produced during the attempt
Delivery	What happened when AVA published the result
Next retry	The next queued retry time, when available

Safe error details

Publication errors are sanitized before they appear in Activity. They help you identify delivery problems without exposing report instructions or hotel data.

A Scheduled Report Still Fails

What you see: Activity shows Retries exhausted, Retry stopped, or Retry publication failed.

Fix:

1. Open the Activity row and note the Execution result and reason.
2. Review the sanitized publication error, if one appears.
3. Check whether the schedule or agent changed during the retry window.
4. Confirm the destination group still has permission to receive the report.
5. Run the report again during a controlled test period.
6. Contact support if the same schedule repeatedly reaches the terminal status.

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

Related Guides

• Set Up Your Chatbot
• Manage Chatbot Documents