Cannot complete Crusader Kings III: Collection / help creating ticket

[Thyfate]

Hi to all,

I have bought all the items (except one see below) from the Crusader Kings III: Collection through an official steam key reseller.

The bundle includes an additional cosmetic DLC "Elegance of the Empire" which I should be able to get by "buying" the remaining bundle. However given I own all paid DLCs, the bundle is priced 0. And now each time I try to "add to account", I get an error dialog box "There was a problem adding this product to your account. Please try again later." and each time I try to "buy" for 0 euro I get an error message saying: "
An unexpected error has occurred. Your purchase has not been completed.
Please wait a few minutes and try again.
If you encounter this error repeatedly, please contact Steam Support.
"

I cannot find a way to navigate through the support and help system to find a way to create a ticket:
- when I click on the game, and then on "I cant successfully purchase", I am led back to the initial game selection screen
- when I look at my transactions, there is no trace of this "unsuccessful" purchase and so I cannot create a ticket for it

Thanks in advance for your help

[Cathulhu]

You can not buy games or bundles below a certain price. Should be about 50Cents or a buck. That error is intentional. Sorry, there are already safeguards in place so that pricing errors are not abused.

By the way, your link is broken.

[Thyfate]

Thanks for your answer but the publisher intention was clearly to let people who own the full set be able to get the additional DLC so I am looking for a way to circumvent what is more a bug than an "intentional error" in this case. Link fixed by the way

[Cathulhu]

Ask the publisher to fix the bundle then.

[Thyfate]

For people finding this post, found a solution, thanks to Paradox support, it was to buy another game at the same time to get a basket with an amount different from 0

Wish I could have easily found this "fix" here, though it's definitely more a steam bug than anything else given the nature of this workaround