Cron type trigger
    • PDF

    Cron type trigger

    • PDF

    Article Summary

    Available in VPC

    You can create Cron type triggers in the NAVER Cloud Platform console's Cloud Functions > Trigger. Cron type triggers provide the feature to run a specific action at regular intervals. This characteristic makes Cron type triggers useful to run scheduled jobs regularly like monitoring. It could be used to replace brief batch jobs of CI tools such as Jenkins.
    Refer to Running action or trigger and Trigger for how to run and monitor triggers that have been created.

    Create triggers

    A Cron type trigger is a type of feed that guarantees regular execution based on a certain time according to the user's request.

    Set execution options

    Setting execution options for Cron type triggers is done in the console's Cron information settings.

    compute-15-3-101.png

    Cyclic execution may be scheduled according to user settings in Cron information settings. Once registered, the trigger will be run in cycles until the execution options are modified or deleted. The execution cycle can be set by using the selection box on the right or by the user's input. The following is the basic example of the execution options.

    */5 * * * *: Run every 5 minutes.
    0 10 * * *: Run every day at 10:00 AM.
    0 10 5 * *: Run on the 5th of every month at 10:00 AM.
    0 10 5 9 *: Run on October 5 every year at 10:00 AM.
    0 10 * * 1: Run on every Monday at 10:00 AM.
    
    • The execution option uses the syntax from Unix crontab by default. 5 fields are separated by spaces. Refer to http://crontab.org for detailed information about each field.
    • The monthly input range is 0 (January) to 11 (December).
    • The input range for days of the week is 0 (Sunday) to 6 (Saturday).

    Restrictions

    The following are the restrictions in using Cron type triggers.

    • The restrictions of basic actions also apply to the actions connected to Cron type triggers. Accordingly, an action's maximum execution time possible is limited to 5 minutes (300 seconds). Jobs that exceed 5 minutes are not supported by the current version.
    • The number of times an action can be run is restricted by a contract. If the number of uses reaches or exceeds the limit, then the cyclic execution may not be guaranteed.

    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.