Production errors being thrown

[irvingpop]

Capturing these errors from stdout on the container:

$ kubectl -n operationcode logs -f town-crier-6469f7f8d-7spvs                                                               <aws:operationcode>

> opcode-slack-cron@1.0.0 start /usr/src/app
> node announcer.js

Refreshing the CRON Table
/usr/src/app/node_modules/cron/lib/cron.js:413
				throw new Error('Unknown alias: ' + alias);
				^

Error: Unknown alias: und
    at /usr/src/app/node_modules/cron/lib/cron.js:413:11
    at String.replace (<anonymous>)
    at CronTime._parse (/usr/src/app/node_modules/cron/lib/cron.js:406:29)
    at new CronTime (/usr/src/app/node_modules/cron/lib/cron.js:46:9)
    at new CronJob (/usr/src/app/node_modules/cron/lib/cron.js:527:19)
    at /usr/src/app/announcer.js:82:35
    at Array.forEach (<anonymous>)
    at page (/usr/src/app/announcer.js:65:17)
    at /usr/src/app/node_modules/airtable/lib/query.js:102:17
    at Request._callback (/usr/src/app/node_modules/airtable/lib/run_action.js:68:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! opcode-slack-cron@1.0.0 start: `node announcer.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the opcode-slack-cron@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-11-11T18_14_00_593Z-debug.log

I can confirm that the container image we're using is the one from 2019, so I'd guess the breakage is external (perhaps an API changed?)