|
| 1 | +--- |
| 2 | +title: Schedule a User Data Function |
| 3 | +description: Learn how to configure a scheduled trigger for a User Data Function in Microsoft Fabric using the built-in Job Scheduler. |
| 4 | +ms.reviewer: mksuni |
| 5 | +ms.date: 07/07/2026 |
| 6 | +ms.topic: how-to |
| 7 | +--- |
| 8 | + |
| 9 | +# Schedule a User Data Function |
| 10 | + |
| 11 | +Microsoft Fabric Job Scheduler enables you to run User Data Functions (UDFs) on a recurring schedule without requiring a pipeline, notebook, or external orchestration service. You can configure schedules directly on a User Data Function, specify recurrence patterns, pass function parameters, and monitor executions from the Fabric monitoring experience. |
| 12 | + |
| 13 | +## Prerequisites |
| 14 | + |
| 15 | +Before creating a schedule, ensure that: |
| 16 | + |
| 17 | +- You have a published User Data Function. |
| 18 | +- You have Contributor or higher permissions on the workspace. |
| 19 | +- The function is tested successfully by using manual invocation. |
| 20 | +- You configure any required connections, secrets, or dependencies. |
| 21 | + |
| 22 | +## Use cases |
| 23 | + |
| 24 | +Schedule User Data Functions to automate recurring business and operational tasks. Common scenarios include: |
| 25 | + |
| 26 | +- **Data quality validation** – Run checks on datasets before reporting or downstream processing. |
| 27 | +- **Customer feedback processing** – Analyze new feedback, generate sentiment scores, and store results. |
| 28 | +- **Business event generation** – Detect changes in operational data and publish business events for downstream applications. |
| 29 | +- **Scheduled cleanup** – Archive old records, remove temporary files, or perform routine maintenance tasks. |
| 30 | +- **Periodic data synchronization** – Sync data from external systems into Fabric on a recurring schedule. |
| 31 | +- **Automated notifications** – Generate alerts or notifications based on business rules and thresholds. |
| 32 | + |
| 33 | +## Open the scheduler |
| 34 | + |
| 35 | +1. Open your Fabric workspace. |
| 36 | +1. Open the User Data Function item. |
| 37 | +1. Select **Settings**. |
| 38 | +1. Select **Schedule**. |
| 39 | + |
| 40 | +The **Schedule** page enables you to: |
| 41 | + |
| 42 | +- Create schedules |
| 43 | +- Configure failure notifications |
| 44 | +- View scheduled executions |
| 45 | +- Edit or disable schedules |
| 46 | +- Manually run scheduled jobs |
| 47 | + |
| 48 | +## Create a schedule |
| 49 | + |
| 50 | +1. On **Schedule**, select **Add schedule**. |
| 51 | +1. Configure the schedule properties. |
| 52 | + |
| 53 | + The scheduler supports the following settings: |
| 54 | + |
| 55 | + | Setting | Description | |
| 56 | + |----------|-------------| |
| 57 | + | Controller | Variable used to control execution from Variable library | |
| 58 | + | Repeat | Defines the recurrence pattern | |
| 59 | + | Interval | Frequency interval | |
| 60 | + | Start date and time | When the schedule begins | |
| 61 | + | End date and time | When the schedule expires | |
| 62 | + | Time zone | Time zone for schedule execution | |
| 63 | + | Parameters | Input parameters passed to the function | |
| 64 | + |
| 65 | + Select how often the function should run and provide the scheduling details. The scheduler supports recurring executions such as every few minutes, hourly, daily, weekly, or monthly. For example, to run a function every 15 minutes, configure: |
| 66 | + |
| 67 | +1. Provide parameters to function as input. The scheduler can pass parameter values directly to the User Data Function during execution. |
| 68 | + |
| 69 | + > [!IMPORTANT] |
| 70 | + > Parameter names must exactly match the User Data Function signature. Parameter names are case-sensitive. |
| 71 | +
|
| 72 | +1. Save the schedule. |
| 73 | +1. Add more schedules for other functions in your User Data Function item. |
| 74 | + |
| 75 | +## Run a scheduled function manually |
| 76 | + |
| 77 | +To test a scheduled function immediately, select **Run**. Fabric submits an execution without waiting for the next scheduled interval. Manual execution is useful for validating parameters, verifying connections, and testing function logic. |
| 78 | + |
| 79 | +## Monitor scheduled executions |
| 80 | + |
| 81 | +You can monitor User Data Function executions from the Fabric monitoring experience. |
| 82 | + |
| 83 | +1. Open **Monitor Hub**. |
| 84 | +1. Select **Activities**. |
| 85 | +1. Filter by **User data functions**. |
| 86 | + |
| 87 | +Use the monitoring experience to troubleshoot failed executions and validate successful runs. |
| 88 | + |
| 89 | +## Configure failure notifications |
| 90 | + |
| 91 | +You can configure email notifications for failed scheduled runs. |
| 92 | + |
| 93 | +1. Open the **Schedule** page. |
| 94 | +1. In **Failure notifications**, enter one or more email addresses. |
| 95 | +1. Save the configuration. |
| 96 | + |
| 97 | +Fabric sends email notifications whenever a scheduled execution fails. |
| 98 | + |
| 99 | +## Next steps |
| 100 | + |
| 101 | +- Learn about User Data Functions. |
| 102 | +- Learn about Job Scheduler in Microsoft Fabric. |
| 103 | +- Monitor and troubleshoot Fabric workloads using the Monitor hub. |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments