지정된 시간에 함수를 실행하도록 예약하려면 onSchedule 핸들러를 사용하여 Cloud Scheduler를 통해 해당 주제의 이벤트를 트리거하는 Pub/Sub 주제를 만듭니다.
시작하기 전에
결제는 필수지만 각 Cloud Scheduler 작업의 월별 비용은 $0.10(USD)이고 Google 계정당 작업이 3개까지 무료로 허용되므로 전반적인 비용은 부담스럽지 않은 수준일 것입니다. Blaze 가격 계산기를 사용하여 예상 사용량에 따른 예상 비용을 확인해 보세요.
프로젝트에 Pub/Sub 및 Cloud Scheduler API를 사용 설정해야 합니다. 대부분의 Firebase 프로젝트에는 이미 사용 설정되어 있어야 하며 Google Cloud 콘솔에서 사용 설정 여부를 확인할 수 있습니다.
예약 함수 작성
Cloud Functions for Firebase에서 일정 예약 로직은 별다른 배포 시간 요구사항 없이 함수 코드에 상주하고 있습니다. 예약된 함수를 만들려면 functions.pubsub.schedule('your schedule').onRun((context))을 사용합니다.
예를 들어 App Engine cron.yaml 구문을 사용하여 5분마다 함수를 실행하려면 다음과 같이 작성하면 됩니다.
exports.scheduledFunction=functions.pubsub.schedule('every 5 minutes').onRun((context)=>{functions.logger.log('This will be run every 5 minutes!');returnnull;});
Unix Crontab 및 App Engine 구문은 모두 Cloud Scheduler에서 지원됩니다. 예를 들어 Crontab을 사용하여 예약 함수를 실행할 특정 시간대를 선택하려면 다음과 같이 작성하면 됩니다.
exports.scheduledFunctionCrontab=functions.pubsub.schedule('5 11 * * *').timeZone('America/New_York')//Userscanchoosetimezone-defaultisAmerica/Los_Angeles.onRun((context)=>{functions.logger.log('This will be run every day at 11:05 AM Eastern!');returnnull;});
[[["이해하기 쉬움","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-05(UTC)"],[],[],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."]]