Cron scheduled syntax is rejected

[chris-hailstorm]

Maybe a bug in the service, maybe a doco bug, I can't tell --

1. Using this serverless.yml:

service: xxxxxxxx

provider:
    name: aws
    runtime: python2.7
    stage: prod
    region: us-east-1

package:
    exclude:
        - __vendored-**

functions:
    run:
        handler: handler.run
        timeout: 20
        events:
            - schedule:
                cron: cron(5 8 * * ? *)
                enabled: false

Produces this error:
Serverless Error ---------------------------------------

 Missing "rate" property for schedule event in function
 run The correct syntax is: schedule: rate(10 minutes)
 OR an object with "rate" property. Please check the
 docs for more info.

The documentation at https://serverless.com/framework/docs/providers/aws/events/schedule/ suggests this events / schedule / cron syntax would be OK.

1. Single-line variation (with no enabled field):

service: xxxxxxxx

provider:
    name: aws
    runtime: python2.7
    stage: prod
    region: us-east-1

package:
    exclude:
        - __vendored-**

functions:
    run:
        handler: handler.run
        timeout: 250
        events:
            - schedule: cron(5 8 * * ? *)

This variation works fine.

[rowanu]

Yep, this is a bug bug. It's an issue with the schedule object check.

I will submit a fix.

[rowanu]

Upon closer inspection, this is not a bug 😕 Probably just needs some better examples in the docs using the cron syntax.

Change your cron property name in your schedule event to rate and it will work i.e.:

...
        events:
            - schedule:
                rate: cron(5 8 * * ? *)
                enabled: false

[chris-hailstorm]

Confirmed

[chris-hailstorm]

Now using Serverless v1.1.0, this cron syntax is failing:

    funcname:
        events:
            - schedule:
                rate: cron(0 5 * * * ?)

with this error message:

Serverless: Deployment failed!

  Serverless Error ---------------------------------------

     An error occurred while provisioning your stack: SenderEventsRuleSchedule1
     - Parameter ScheduleExpression is not valid..

The rate: rate(5 minutes) syntax is working, but the cron-ized version fails.

[rowanu]

You cannot have a "?" in the year (last) field (as per the docs).

I think you mean to use:

rate: cron(0 5 * * ? *)

[pmuens]

Closing this one as @rowanu provided a solution 👍

Let us know if this is still an issue!

[veerarajuthuta]

schedule rate "cron" not yet supported!
scheduler: invalid, schedule syntax
Scheduling [pullDataFromQueue] cron: [undefined] input: undefined

we are facing this error

[pgrzesik]

Hello @veerarajuthuta - could you please share full details about your problem? It would be great to include reproducible example as well as the full output with the error.

[milkstork-kevin]

The error "scheduler: invalid, schedule syntax" is coming from the serverless-offline package and it seems to be due to the fact that scheduling isn't supported by the package right now.

[RavenHursT]

events:
    - schedule: rate(10 minutes)

works just fine for serverless-offline... So it's just rate: cron([whatever]) that isn't supported?

Is this documented anywhere?

[mnapoli]

@RavenHursT you can open an issue in the plugin's repository.

[RavenHursT]

@mnapoli So... I take it that's a "no"?

[mnapoli]

@RavenHursT that is an issue with the plugin. I don't know if it's documented in the plugin or not, but in any case this should be discussed there.

I don't think pinging people on an unrelated issue from 2016 will yield changes on the plugin.

[RavenHursT]

@mnapoli my mistake.. I was under the impression that serverless-offline was a package maintained by the serverless org.

@dherault any chance you could shed light onto whether or not this caveat it documented somewhere.

Given that so many devs rely upon serverless-offline for local development would it possibly be prudent upon the serverless org to ingest serverless-offline into their ecosystem? 🤔