Route lookup fails on BDS-derived callsigns

[marcus-aa]

When a callsign is marked with "*" , afaik meaning it was derived from a BDS messgae, the route lookup doesn't work properly (or at all)

But if I click on "submit route", it is found without problem.

/M

[marcus-aa]

Or is this related to HP/APF, you had to fix something with it before routes could be entered, here is another one with normal callsign that also doesn't work. But some of them seems work normally.

[marcus-aa]

It showed up but after a while, and now this one also indicated by an asterisk.

[marcus-aa]

When a callsign is marked with "*" , afaik meaning it was derived from a BDS messgae, the route lookup doesn't work properly (or at all)
/M

It looks like they entered APF672_ (with a trailing space), could that be the issue?

[marcus-aa]

No, there is something else going on, possibly related to receiver type, or some other kind of delay.

This one had no route until it more or less landed. No route at 52 minutes, route popped up at 54 minutes. Same callsign.

Could there be an issue looking up callsigns if they are only delivered by JSON receivers?

What triggers the route lookup ?