Can't catch cooldown error

[saig0]

Describe the bug
I use the SDK to extract resources. If a ship extracts resources and the mining laser has a cooldown then the operation fails.

I want to handle the failure case in the process via error event. But currently, I can't catch the error and an incident is created with the message:

409 Conflict
POST https://api.spacetraders.io/v2/my/ships/SG_18_1-3/extract
{"error":{"message":"Ship action is still on cooldown for 30 second(s).","code":4000,"data":{"cooldown":{"shipSymbol":"SG_18_1-3","totalSeconds":70,"remainingSeconds":30,"expiration":"2023-12-22T13:39:48.194Z"}}}}

To Reproduce
Steps to reproduce the behavior:

1. Use the SDK to extract resources two times without waiting in between
2. Verify that an incident is created

Expected behavior
I can catch the cooldown error with the error code cooldownConflictError in the BPMN error event.

Environment

• SDK/Connector template version? 4

Additional context

[saig0]

Resolved by #17. 🚀