雖然系統會針對排定時間執行的函式收費,但整體費用應該不會太高,因為每項Cloud Scheduler工作每月費用為 $0.10 美元,且每個 Google 帳戶可免費執行三項工作。使用 Blaze Pricing Calculator,根據預測用量估算費用。
您必須為專案啟用 Cloud Scheduler API。大多數 Firebase 專案應已啟用這項服務,您可以在 Google Cloud 控制台中確認。
編寫排定函式
在 Cloud Functions for Firebase 中,排程邏輯位於函式程式碼中,沒有特殊的部署時間規定。舉例來說,如要每天清理閒置使用者帳戶,可以編寫以以下匯入陳述式開頭的函式:
Node.js
// The Cloud Functions for Firebase SDK to set up triggers and logging.const{onSchedule}=require("firebase-functions/v2/scheduler");const{logger}=require("firebase-functions");// The Firebase Admin SDK to delete inactive users.constadmin=require("firebase-admin");admin.initializeApp();// The es6-promise-pool to limit the concurrency of promises.constPromisePool=require("es6-promise-pool").default;// Maximum concurrent account deletions.constMAX_CONCURRENT=3;
# The Cloud Functions for Firebase SDK to set up triggers and logging.fromfirebase_functionsimportscheduler_fn# The Firebase Admin SDK to delete users.importfirebase_adminfromfirebase_adminimportauthfirebase_admin.initialize_app()
// Run once a day at midnight, to clean up the users// Manually run the task here https://console.cloud.google.com/cloudschedulerexports.accountcleanup=onSchedule("every day 00:00",async(event)=>{// Fetch all user details.constinactiveUsers=awaitgetInactiveUsers();// Use a pool so that we delete maximum `MAX_CONCURRENT` users in parallel.constpromisePool=newPromisePool(()=>deleteInactiveUser(inactiveUsers),MAX_CONCURRENT,);awaitpromisePool.start();logger.log("User cleanup finished");});
# Run once a day at midnight, to clean up inactive users.# Manually run the task here https://console.cloud.google.com/cloudscheduler@scheduler_fn.on_schedule(schedule="every day 00:00")defaccountcleanup(event:scheduler_fn.ScheduledEvent)-> None:"""Delete users who've been inactive for 30 days or more."""user_page:auth.ListUsersPage|None=auth.list_users()whileuser_pageisnotNone:inactive_uids=[user.uidforuserinuser_page.usersifis_inactive(user,timedelta(days=30))]auth.delete_users(inactive_uids)user_page=user_page.get_next_page()
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-06 (世界標準時間)。"],[],[],null,["\u003cbr /\u003e\n\nIf you want to schedule functions to run at specified times, use\nthe `onSchedule` handler provided by `firebase-functions/v2/scheduler`.\nThese functions use [Cloud Scheduler](https://cloud.google.com/scheduler/)\nto invoke function logic at the times or intervals that you define.\n\nBefore you begin\n\nThough scheduled functions are billed, you can expect the overall\ncost to be manageable, as\neach Cloud Scheduler job costs $0.10 (USD) per month, and there is an\nallowance of three jobs per Google account, at no charge. Use the Blaze\n[pricing calculator](/pricing#blaze-calculator) to generate a cost estimate\nbased on your projected usage.\n\nThe Cloud Scheduler API must be enabled for your\nproject. It should already be enabled for most Firebase projects; you can\nverify in the [Google Cloud console](https://console.cloud.google.com/).\n\nWrite a scheduled function\n\nIn Cloud Functions for Firebase, scheduling logic resides in your functions code,\nwith no special deploy-time requirements.\nFor example, to clean up inactive user accounts once daily, you could write\na function starting with the following import statements: \n\nNode.js \n\n // The Cloud Functions for Firebase SDK to set up triggers and logging.\n const {onSchedule} = require(\"firebase-functions/v2/scheduler\");\n const {logger} = require(\"firebase-functions\");\n\n // The Firebase Admin SDK to delete inactive users.\n const admin = require(\"firebase-admin\");\n admin.initializeApp();\n\n // The es6-promise-pool to limit the concurrency of promises.\n const PromisePool = require(\"es6-promise-pool\").default;\n // Maximum concurrent account deletions.\n const MAX_CONCURRENT = 3; \n https://github.com/firebase/functions-samples/blob/c4fde45b65fab584715e786ce3264a6932d996ec/Node/delete-unused-accounts-cron/functions/index.js#L20-L31\n\nPython \n\n # The Cloud Functions for Firebase SDK to set up triggers and logging.\n from firebase_functions import scheduler_fn\n\n # The Firebase Admin SDK to delete users.\n import firebase_admin\n from firebase_admin import auth\n\n firebase_admin.initialize_app() \n https://github.com/firebase/functions-samples/blob/c4fde45b65fab584715e786ce3264a6932d996ec/Python/delete-unused-accounts-cron/functions/main.py#L19-L26\n\nThen, you could use `onSchedule` to start a Cloud Scheduler task: \n\nNode.js \n\n // Run once a day at midnight, to clean up the users\n // Manually run the task here https://console.cloud.google.com/cloudscheduler\n exports.accountcleanup = onSchedule(\"every day 00:00\", async (event) =\u003e {\n // Fetch all user details.\n const inactiveUsers = await getInactiveUsers();\n\n // Use a pool so that we delete maximum `MAX_CONCURRENT` users in parallel.\n const promisePool = new PromisePool(\n () =\u003e deleteInactiveUser(inactiveUsers),\n MAX_CONCURRENT,\n );\n await promisePool.start();\n\n logger.log(\"User cleanup finished\");\n }); \n https://github.com/firebase/functions-samples/blob/c4fde45b65fab584715e786ce3264a6932d996ec/Node/delete-unused-accounts-cron/functions/index.js#L35-L49\n\nPython \n\n # Run once a day at midnight, to clean up inactive users.\n # Manually run the task here https://console.cloud.google.com/cloudscheduler\n @scheduler_fn.on_schedule(schedule=\"every day 00:00\")\n def accountcleanup(event: scheduler_fn.ScheduledEvent) -\u003e None:\n \"\"\"Delete users who've been inactive for 30 days or more.\"\"\"\n user_page: auth.ListUsersPage | None = auth.list_users()\n while user_page is not None:\n inactive_uids = [\n user.uid for user in user_page.users if is_inactive(user, timedelta(days=30))\n ]\n auth.delete_users(inactive_uids)\n user_page = user_page.get_next_page() \n https://github.com/firebase/functions-samples/blob/c4fde45b65fab584715e786ce3264a6932d996ec/Python/delete-unused-accounts-cron/functions/main.py#L31-L42\n\nBoth Unix Crontab and App Engine syntax\nare supported by Cloud Scheduler. For example, to use Crontab, do something like this: \n\nNode.js \n\n exports.scheduledFunctionCrontab = onSchedule(\"5 11 * * *\", async (event) =\u003e {\n // ...\n });\n\nPython \n\n @scheduler_fn.on_schedule(schedule=\"5 11 * * *\")\n\n| **Important:** Depending on how you design your scheduling logic, a function may be triggered multiple times, with the next instance running while the previous instance is still executing.\n\nDeploy a scheduled function\n\nWhen you deploy a scheduled function, a scheduler job and an HTTP function\nare created automatically. The Firebase CLI echoes the function name,\nand you can view the job and the function in the\n[Google Cloud console](https://console.cloud.google.com/project/_/cloudscheduler).\nThe topic is named according to the following convention:\n\n**firebase-schedule-\u003cvar translate=\"no\"\u003efunction_name\u003c/var\u003e-\u003cvar translate=\"no\"\u003eregion\u003c/var\u003e**\n\nFor example:\n\n**firebase-schedule-accountcleanup-us-east1.**\n\nAt the scheduled time, the default compute service account invokes the\nassociated HTTP function. This means that only the associated Cloud Scheduler\njob has permission to run the function.\n| **Important:** Make sure you do not manually delete or modify the function or scheduler job in the console. Doing this could cause errors in the execution of your scheduled function."]]