Forum Discussion

ADuToit's avatar
ADuToit
Icon for Participant rankParticipant
2 months ago

Powerflow Application Queue Trigger Failure

Hi All,

I've Developed a Runbook Action within ScienceLogic, that triggers a Powerflow Application if certain Runbook Automation Policy conditions are met.

Upon execution, it sends the following payload:

"params": {
     "configuration": configuration,
     "event_policy_name": EM7_VALUES['%_event_policy_name'],
     "event_details": EM7_VALUES,
     "organization_name": EM7_VALUES['%O'],
     "system_url": system_url,
     "queue": queue
}

These parameters are specified as inputs, and some are derived from the EM7Values.

When the Runbook Automation linked to this Action executes against a specific Event Policy raised on a Device, i can see a success message in the "Event Notifications" window, and i can see all inputs and variables are passed through in its entirety.

The real issue comes when you open Powerflow. The Application immediately fails, and an error message stating that theres an "Internal Request Error: pop from empty list". This error doesnt make any logical sense as the parameters i pass through are either JSON or String Payloads, no Arrays.

I've been doing testing with the payloads, ensuring that the configuration being referenced exists, and confirmed all these are in place and are working fine.

I then removed the "queue" value from the params body, and only passed the rest of the parameters, this succeeds and the application executes without incident. What's interesting, even if manually executing the application in the UI with a custom parameter set, as soon as you specify the queue, it fails.

Now its important to know that we've only recently created the queues on a development system, and this is the first time we're testing with the newly created queues.

I was hoping that someone in this community might be able to shed some light as to why this might be happening? Could it be that the queues are unreachable, and therefor when not specifying the custom queue, it defaults to the celery queue, which are reachable, and therefor works?

If the queues are the problem, what could be done to try and fix the problem?

Any and all contributions are welcome.
Sincerely

Andre

No RepliesBe the first to reply