[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Admin settings - Schedule History\n\nThe **Schedule History** page in the **Alerts \\& Schedules** section of the **Admin** menu shows the recent history of the Scheduler's activity.\n| **Note:** If you have a permission that provides access to only select pages in the Admin panel, such as [`manage_schedules`](/looker/docs/admin-panel-users-roles#manage_schedules), [`manage_themes`](/looker/docs/admin-panel-users-roles#manage_themes), or [`see_admin`](/looker/docs/admin-panel-users-roles#see_admin), but you don't have the [Admin role](/looker/docs/admin-panel-users-roles#default_roles), the page or pages that are described here may not be visible to you in the Admin panel.\n\nYou can view scheduler plans on the [Admin settings - Schedules](/looker/docs/admin-panel-alerts-and-schedules-schedule) page. The schedule plan specifies when content should be sent to specific addresses.\n\nA new schedule job is created each time that content is sent. For example, if a schedule specifies sending specific content to certain addresses every Monday, then Looker will make a new scheduler job each Monday to send that content to the specified addresses.\n\nScheduling status\n-----------------\n\nAt the top of the Scheduler History page, you can filter the scheduled jobs by status:\n\n- **All**: all recent scheduler jobs\n- **Running**: only scheduler jobs that are currently running\n- **Successful**: only scheduler jobs that completed successfully\n- **Failed**: only scheduler jobs that failed to complete successfully\n\nInformation included\n--------------------\n\nUsing error messages\n--------------------\n\nUse error messages to debug scheduled jobs. For example, if the owner of a schedule is missing a permission or the owner's user ID is not enabled when a schedule was run on their behalf, the job fails.\n\nAnother example is scheduled jobs that fail in the scheduled job queue without the job having been closed. The Scheduler monitors the scheduled job queue for jobs that have been enqueued for an hour or more while more recent jobs have been successfully dequeuing. If this occurs, the enqueued scheduled job is closed and reported as **Failed** on the **Schedule History** page, returning one of the following messages:\n\n- Job is no longer processing `@\u003cstate\u003e` (where `\u003cstate\u003e` is either **execute** or **deliver**)\n- Job was expected to dequeue by `@\u003ctime\u003e`\n\nIf you see one of these messages, your scheduled job will execute the next time it is scheduled to run.\n\n\nGetting additional details\n--------------------------\n\nClick the **Details** button to the right of any schedule to view additional information, including recipient addresses, whether the row limit was reached, the start and end times, and other details about the scheduled job. For scheduled content that uses a datagroup, the Details window will also show the model and the name of the datagroup that is being used as the schedule trigger."]]
