What are the possible causes and remedies if a "Trigger Other Builds" Step repeatedly logs the message "Triggered build id not found in cache, continue to query from server..."?

We had a build where a "Trigger Other Builds" step had a log that started with:

22:03:11,962 INFO  - Running step...
22:08:12,465 TRACE - Triggered build id not found in cache, continue to query from server...
22:13:12,477 TRACE - Triggered build id not found in cache, continue to query from server...
22:18:12,490 TRACE - Triggered build id not found in cache, continue to query from server...

It continued to repeat the "Triggered build id not found in cache" message for about 4 hours until I manually cancelled the build.

On the Configuration Overview page of the configuration that would have been triggered, there were zero active Build Requests, nothing having Process Status of RUNNING_BUILD, WAITING_PROCESS, or anything else. There was also no Error Message box on the Configuration Overview.

The node that the configuration would have run on was up and available. When I re-ran the configuration containing the Trigger step, it successfully started a build of the target configuration.