The bot was working fine few months ago when I tested it, now I receive errors:

Jan 16, 2024, 10:03:23 PM
TypeError: Cannot read properties of undefined (reading 'startsWith')
    at getLimitByModel (/var/task/customer_code.js:628:3012)
    at predict (/var/task/customer_code.js:628:3267)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /var/task/customer_code.js:628:4626
    at async /var/task/customer_code.js:127:170

Jan 16, 2024, 10:03:23 PM
[6cf8cd3121]    [dm]    :     An unexpected error occurred.
  [TypeError, Cannot read properties of undefined (reading 'startsWith')]

Report-id: d5df604b-4c42-4194-8e23-3bbd6680d1ad

Hey @ripe-van-56531 I went to check the error report and got a notification it doesn't exist. Can you let me know if you are still having a problem with this and if so get a new report ID for me.

Hi @flat-plumber-75402 , where should I check that? I rebuilt the bot based on the old one, and that is working fine, but I'm still curios what was the problem.

So the new bot is working fine?

Hi @flat-plumber-75402 Yes, the new bot was working fine until now, now I'm not able to publish any of my bots:

Jan 31, 2024, 3:01:24 PM
error in handler fe [Error]: An unexpected error occurred when trying to process your request. (Error ID: err_20240131130124x548698C2)
    at Bc (/var/task/customer_code.js:11:62529)
    at Nt (/var/task/customer_code.js:11:62351)
    at R (/var/task/customer_code.js:11:71961)
    at /var/task/customer_code.js:11:64049
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.onTrigger (/var/task/customer_code.js:649:9675)
    at async handler (/var/task/customer_code.js:1027:1823)
    at async /var/task/index.js:20:13702
    at async handleHTTPEvent (/var/task/index.js:20:13678)
    at async Runtime.handler (/var/task/index.js:20:13567) {
  isApiError: true,
  code: 500,
  description: 'An unknown error occurred',
  type: 'Unknown',
  error: undefined,
  id: 'err_20240131130124x548698C2'
}

Hello @ripe-van-56531 I apologize in the length before a response. I was out of office. Just to confirm is this still an onging issue?

Hi @flat-plumber-75402 No problem, it is solved now. Looks like it was a system wide issue, but thank you!