You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PFDL Scheduler schedules services, which are then executed on some asset. In case that the service execution succeedes, a notification is send to the PFDL scheduler, which then triggers an event (Event(event_type="service_finished", data={"service_id": service_uuid}).
However, there is no specified behavior in case that an service execution fails and the process execuion should be aborted.
Here, it would be great if a custom event type could be provided, that stops the scheduler execution.
For example the event could be Event(event_type="service_failed", data={"service_id": service_uuid}) to stop the scheduler.
Another nice feature would be an Event Type to reschedule the service execution, so that the scheduler again starts the failed service execution. An event coul be e.g., Event(event_type="service_repeat", data={"service_id": service_uuid})
The text was updated successfully, but these errors were encountered:
The PFDL Scheduler schedules services, which are then executed on some asset. In case that the service execution succeedes, a notification is send to the PFDL scheduler, which then triggers an event (Event(event_type="service_finished", data={"service_id": service_uuid}).
However, there is no specified behavior in case that an service execution fails and the process execuion should be aborted.
Here, it would be great if a custom event type could be provided, that stops the scheduler execution.
For example the event could be Event(event_type="service_failed", data={"service_id": service_uuid}) to stop the scheduler.
Another nice feature would be an Event Type to reschedule the service execution, so that the scheduler again starts the failed service execution. An event coul be e.g., Event(event_type="service_repeat", data={"service_id": service_uuid})
The text was updated successfully, but these errors were encountered: