---
schema_version: "1"
id: b7ffafb7663205084cae9c7ab8b2c470bf37e9625b57b7fa97693326d7ead234
title: Why is my scheduled recipe not running as expected?
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/bi_integrate_troubleshoot_event_based_scheduling.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.bi_integrate_troubleshoot_event_based_scheduling.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b29db1e1eaa59096fa53039e2e39a00811e0b1606302a83eff39ddf956a2a666
description: When recipes use scheduling, users can see unexpected results or sometimes no results at all. Here are some common reasons why your recipe might be having issues.
products:
  - CRM Analytics
  - Cross Cloud
release: "264"
---
# Why is my scheduled recipe not running as expected?

When recipes use scheduling, users can see unexpected results or sometimes no results at all. Here are some common reasons why your recipe might be having issues.

## My recipe with an event-based schedule didn't run

When recipes are chained together with event-based scheduling, unscheduling or manually running an upstream recipe or connection can result in unexpected outcomes.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-analytics-bi-264-0-0-production-enus/ec791473-f5b4-4f64-a656-9104f455d966/images/icon_note.png)

Note When a recipe schedule is dependent on multiple events, after it runs, it doesn’t run again until all the dependent events have also rerun. Take a recipe that is dependent on 2 external objects, 2 local Salesforce objects, and 1 external CSV upload. After the recipe runs, it only runs again after each of the 5 events (2 external object refreshes, 2 local object refreshes, and 1 CSV upload) have rerun. Therefore, before following this troubleshooting, check that the recipe’s previous run is before the last run of all the triggering events. For example, check the date of the recipe’s last run to ensure it is before the last run of the 2 external data refreshes, the 2 local object refreshes, and the CSV upload.

To check whether an unscheduled recipe is the cause:

- Open the recipe that’s not behaving as expected. If it isn’t scheduled, schedule it.
- If you don’t find an issue in the first recipe, check whether the preceding recipe is scheduled.
- Continue working back through the chain as needed.

If you find no unscheduled recipes in the chain, check that the data input sources are included in a scheduled connection.

If an unscheduled recipe or connection isn’t the cause, a triggering recipe or connection executed using the Run now option could be the problem. To resolve this situation:

- Wait until the item is triggered automatically.
- Manually run all upstream triggers for the recipe, starting with the first recipe.

If you can’t find a cause, unschedule all the upstream recipes and connections and then reschedule them, starting with the first recipe. This action resets the chain.

## My scheduled recipe didn't run and I see no errors

When a scheduled recipe, time-based or event-based, becomes invalid due to any missing datasets or other configuration issues, the recipe doesn't start, regardless of the schedule. If a recipe doesn't start, it doesn't show up in the job monitor. This means that you don't get a recipe job error or any notification that the recipe has an error. Open the recipe in the recipe editor to find any errors and fix them. When the recipe is valid again, the scheduled job runs as expected.