I am trying to define some constraints on some tables in my database:

Destinations : ID (PK), Description
Pallets : ID (PK), ID_Destination1 , ID_Destination2

I would like to define ID_Destination1 and ID_Destination2 as foreign keys referencing ID of Destinations .

However, when I try to define these foreign keys with constraints ON UPDATE CASCADE and ON DELETE SET NULL , I get the following error:
Introducing FOREIGN KEY constraint 'FK_PalletDest1' on table 'Pallets' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints.

I managed to create the table defining only one foreign key with constraint ON UPDATE SET NULLON DELETE SET NULL , but I couldn't create both foreign keys.

I read that one solution could be to set ON UPDATE NO ACTION and ON DELETE NO ACTION and to manage update/delete of Destinations within the code.

Why do these relations maybe cause cycles?

How do I bypass this error?