Instanceof Error not working

[aleguern-azivko]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

The AWS SDK v3 type definitions for EventBridge Scheduler's ResourceNotFoundException are not properly exposed, forcing unsafe type casting to handle this common error case.

Current workaround:

if ((error as any).name === 'ResourceNotFoundException')

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/client-scheduler: ^3.716.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

22

Reproduction Steps

import { ResourceNotFoundException, GetScheduleCommand } from '@aws-sdk/client-scheduler';

try {
  await scheduler.send(new GetScheduleCommand({ Name: 'non-existent' }));
} catch (error) {
  // Have to use unsafe casting
  if (error instanceof ResourceNotFoundException) {
    // Handle missing schedule
   console.log("hello world")
  }
}

Observed Behavior

ResourceNotFoundException: Schedule non-existent does not exist.

Expected Behavior

logging hello worl

Possible Solution

No response

Additional Information/Context

No response

[zshzbh]

Hello @aleguern-azivko ,

This error seems like it's not from AWS SDK. You need to initialize the scheduler client first. Here's the corrected code:

import {ResourceNotFoundException, SchedulerClient, GetScheduleCommand } from '@aws-sdk/client-scheduler';

// Initialize the scheduler client
const scheduler = new SchedulerClient({
  region: "us-east-1" // Replace with your desired region
});

try {
  await scheduler.send(new GetScheduleCommand({ Name: 'non-existent' }));
} catch (error) {
  if (error instanceof ResourceNotFoundException) {
    // Handle missing schedule
    console.log("hello world");
  } else {
    // Handle other types of errors
    console.error("Other error:", error);
  }
}

And then you can see hello world

➜  6884 node index.mjs
hello world

[zshzbh]

If you simple catch the error and log the error using the code I posted above, you can see

ResourceNotFoundException: Schedule non-existent does not exist.
    at de_ResourceNotFoundExceptionRes (/Users/xxxx/Desktop/newProj/Issues6000s/node_modules/@aws-sdk/client-scheduler/dist-cjs/index.js:813:21)

which indicates it's from node_modules/@aws-sdk/client-scheduler

[aleguern-azivko]

Ok I think I found the problem, I imported correctly the client
const scheduler = new SchedulerClient({}); but the ResourceNotFoundException came from@aws-sdk/client-dynamodb instead of the scheduler library.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[zshzbh]

Hey @aleguern-azivko ,

ResourceNotFoundException does exist in @aws-sdk/client-scheduler.

But since you didn't initiate the client, so another error got caught before reaching the part that causesResourceNotFoundException

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.