Scheduled functions in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a scheduled function in Firebase?

A scheduled function in Firebase is a cloud function that runs automatically at set times or intervals, like a timer that triggers tasks without manual action.

beginner

How do you define the timing for a scheduled function in Firebase?

You define the timing using a cron expression or a predefined schedule string that tells Firebase when to run the function, such as every hour or every day at midnight.

beginner

Why use scheduled functions instead of manual triggers?

Scheduled functions automate repetitive tasks, save time, and ensure tasks run reliably at specific times without needing someone to start them manually.

intermediate

What Firebase package do you import to create scheduled functions?

You import 'firebase-functions' and use the 'functions.pubsub.schedule()' method to create scheduled functions.

intermediate

Give an example of a cron expression to run a function every day at 3 AM.

The cron expression is '0 3 * * *', which means at minute 0, hour 3, every day, every month, every weekday.

What does a scheduled function in Firebase do?

A Runs when a file is uploaded

B Runs only when a user clicks a button

C Runs only during development

D Runs automatically at set times

Scheduled functions run automatically based on a set schedule, not triggered by user actions or file uploads.

Which method is used to schedule a function in Firebase?

A functions.storage.object()

B functions.pubsub.schedule()

C functions.auth.user()

D functions.database.ref()

The 'pubsub.schedule()' method is used to create scheduled functions in Firebase.

What does the cron expression '0 0 * * *' mean?

A Run every day at midnight

B Run every hour

C Run every minute

D Run every Sunday

'0 0 * * *' means run at minute 0, hour 0 every day, which is midnight daily.

Why are scheduled functions useful?

A They require user input to run

B They only run during app deployment

C They automate tasks without manual start

D They replace database triggers

Scheduled functions automate tasks by running on a timer, no manual input needed.

Which Firebase package do you need to import to create scheduled functions?

A firebase-functions

B firebase-auth

C firebase-storage

D firebase-database

'firebase-functions' package provides the tools to create scheduled cloud functions.

Explain how to create a scheduled function in Firebase and set it to run every hour.

Think about the cron syntax and the Firebase method to schedule.

Describe the benefits of using scheduled functions in cloud infrastructure.

Consider why timers help in daily operations.

Practice

1. What is the main purpose of Firebase Scheduled Functions?

easy

A. To run code automatically at specific times without manual intervention

B. To store user data securely in the cloud

C. To create real-time chat applications

D. To manage user authentication and login

Solution

1. Step 1: Understand the role of scheduled functions

   Scheduled functions are designed to run tasks automatically at set times without needing a user to start them.

2. Step 2: Compare with other Firebase features

   Other options like storing data, chat apps, or authentication are handled by different Firebase services, not scheduled functions.

3. Final Answer:

   To run code automatically at specific times without manual intervention -> Option A

4. Quick Check:

   Scheduled functions = automatic timed code run [OK]

Hint: Scheduled functions run code on a timer, no clicks needed [OK]

Common Mistakes:

• Confusing scheduled functions with database storage
• Thinking scheduled functions handle user login
• Assuming scheduled functions manage real-time data

2. Which of the following is the correct way to schedule a Firebase function to run every day at midnight using cron syntax?

easy

A. functions.pubsub.schedule('every day 00:00').onRun(...)

B. functions.pubsub.schedule('daily at midnight').onRun(...)

C. functions.pubsub.schedule('0 0 * * *').onRun(...)

D. functions.pubsub.schedule('midnight every day').onRun(...)

Solution

1. Step 1: Identify correct cron syntax for midnight daily

   The cron expression '0 0 * * *' means minute 0, hour 0, every day, which is midnight daily.

2. Step 2: Match with Firebase schedule method

   Firebase uses cron syntax strings like '0 0 * * *' in schedule() to set times precisely.

3. Final Answer:

   functions.pubsub.schedule('0 0 * * *').onRun(...) -> Option C

4. Quick Check:

   Cron '0 0 * * *' = midnight daily [OK]

Hint: Cron '0 0 * * *' means every day at midnight [OK]

Common Mistakes:

• Using natural language instead of cron syntax
• Incorrect cron format like 'every day 00:00'
• Misplacing hour and minute values in cron

3. Given the following Firebase scheduled function code, what will it log when triggered?

exports.dailyTask = functions.pubsub.schedule('every 5 minutes').onRun((context) => {
  console.log('Task running at', new Date().toISOString());
  return null;
});

medium

A. Logs 'Task running at' once at deployment time only

B. Runs continuously without delay, flooding logs

C. Throws a syntax error due to invalid schedule string

D. Logs 'Task running at' with the current timestamp every 5 minutes

Solution

1. Step 1: Understand the schedule string 'every 5 minutes'

   This string tells Firebase to run the function every 5 minutes automatically.

2. Step 2: Analyze the function behavior

   Each time it runs, it logs the message with the current timestamp in ISO format.

3. Final Answer:

   Logs 'Task running at' with the current timestamp every 5 minutes -> Option D

4. Quick Check:

   Schedule 'every 5 minutes' triggers repeated logs [OK]

Hint: Schedule string 'every 5 minutes' means repeated logs every 5 minutes [OK]

Common Mistakes:

• Thinking it runs only once at deployment
• Assuming schedule string is invalid syntax
• Believing it runs nonstop without delay

4. What is wrong with this Firebase scheduled function code?

exports.cleanup = functions.pubsub.schedule('every 60 minutes').onRun(() => {
  // cleanup code here
});

medium

A. The schedule string 'every 60 minutes' is invalid; should use 'every 1 hour' or cron syntax

B. The function must return a promise or null, missing return statement

C. The function name 'cleanup' is reserved and cannot be used

D. The schedule method requires a timezone parameter

Solution

1. Step 1: Check the schedule string validity

   Firebase does not recognize 'every 60 minutes'; it supports 'every 1 hour' or cron expressions.

2. Step 2: Review other code parts

   Returning a promise or null is recommended but not mandatory here; function name and timezone are not issues.

3. Final Answer:

   The schedule string 'every 60 minutes' is invalid; should use 'every 1 hour' or cron syntax -> Option A

4. Quick Check:

   Invalid schedule string = error [OK]

Hint: Use 'every 1 hour' not 'every 60 minutes' in schedule [OK]

Common Mistakes:

• Using unsupported time phrases in schedule
• Forgetting to return null or a promise
• Assuming timezone is always required

5. You want to create a Firebase scheduled function that runs every Monday at 9:30 AM in New York time to send weekly reports. Which is the correct way to configure this function?

hard

A. functions.pubsub.schedule('every Monday 9:30').timeZone('America/New_York').onRun(...)

B. functions.pubsub.schedule('30 9 * * 1').timeZone('America/New_York').onRun(...)

C. functions.pubsub.schedule('0 9 * * 1').timeZone('EST').onRun(...)

D. functions.pubsub.schedule('30 9 * * 1').onRun(...)

Solution

1. Step 1: Use correct cron syntax for Monday 9:30 AM

   The cron '30 9 * * 1' means minute 30, hour 9, every Monday (day 1).

2. Step 2: Set proper timezone for New York

   Use the full IANA timezone string 'America/New_York' to handle daylight savings correctly.

3. Step 3: Verify other options

   functions.pubsub.schedule('every Monday 9:30').timeZone('America/New_York').onRun(...) uses invalid schedule string; functions.pubsub.schedule('0 9 * * 1').timeZone('EST').onRun(...) uses 'EST' which is not a valid timezone identifier; functions.pubsub.schedule('30 9 * * 1').onRun(...) misses timezone setting.

4. Final Answer:

   functions.pubsub.schedule('30 9 * * 1').timeZone('America/New_York').onRun(...) -> Option B

5. Quick Check:

   Cron + correct timezone = functions.pubsub.schedule('30 9 * * 1').timeZone('America/New_York').onRun(...) [OK]

Hint: Use cron '30 9 * * 1' plus 'America/New_York' timezone [OK]

Common Mistakes:

• Using natural language instead of cron syntax
• Using short timezone codes like 'EST' instead of full IANA names
• Forgetting to set timezone causing wrong run times