Closed eXpl0it3r closed 11 months ago
Root cause analysis:
When disabling the trigger on the Dashboard the WebApi is called, which das a converting from the web DTO to a trigger domain object. The DTO however doesn't contain all the information, e.g. the Definition isn't sent from the frontend to the backend, meaning the trigger information is overwritten with NULL
in the DB and when the next scheduling tick, gets all the reoccurring triggers, it get a NULL
value for the Cron Definition and crashes.
Looking at this, I also spotted that null
as string (not NULL
) is written into the parameters field, as it does a serializing of a C# null string.
Potential fix: Use the saved trigger as basis and only apply changed/non-null values.
Steps to Reproduce
Actual Behavior
The process crashes with the following exception:
Expected Behavior
The trigger successfully fires without server crash