+
Skip to content

Errors when using KeepAlive-style CloudWatch events #369

Open
@danepowell

Description

@danepowell

I have a CloudWatch event that essentially acts as a keepalive function by calling my Alexa Lambda backend with a "matched event" once every 10 minutes.

This generates a ton of errors like this in my logs:

"errorMessage": "Cannot read property 'new' of undefined",
    "errorType": "TypeError",
    "stackTrace": [
        "new alexa.request (/var/task/node_modules/alexa-app/index.js:149:30)",
        "/var/task/node_modules/alexa-app/index.js:227:21",
        "tryCatcher (/var/task/node_modules/bluebird/js/main/util.js:26:23)",
        "Promise._resolveFromResolver (/var/task/node_modules/bluebird/js/main/promise.js:483:31)",
        "new Promise (/var/task/node_modules/bluebird/js/main/promise.js:71:37)",
        "alexa.app.request (/var/task/node_modules/alexa-app/index.js:226:12)",
        "handler (/var/task/node_modules/alexa-app/index.js:357:10)"
    ]

I don't think this is hurting anything, but obviously I'd prefer to see something more constructive and less distracting than those errors.

Is there a better way to build a keepalive function with CloudWatch? Or should alexa-app be a little more resilient when it receives events that it's not expecting?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载