Orchestrator Triggers: Hostname is unresponsive

Hi, everyone. I recently ran into this popup while creating triggers in the Orchestrator:

Previously, all triggers were working fine, but now whenever a trigger fires, the job is stuck in the Pending state and must be manually stopped. Additionally, manually queued jobs have been able to run just fine.

Has anyone else encountered (and resolved) this issue before? I tried digging around but haven’t found anything related so far, any help would be greatly appreciated!

Hi @leeal

Jobs scheduled to be executed by the inactive session remain in a Pending state until the corresponding connection to Orchestrator is made. To acknowledge your selection of the inactive hostname

Check out this document