Custom Context bug 2?

When I set a second custom context as failover of the previous one, a “Bad Destination” message appears on GUI FreePBX Notices.
(despiting this chain is working OK)
Is this a bug or it is correct ? Why ?


Just to be clear:
a dial rule is set
All is set to "Deny Rules"
I tried a second Custom Context as well as an Announcement in failover.
The Notice is:

Custom Context: newcustom1 (newcustom1)

Added 3 minutes ago