Hello community,
I’m encountering some strange behavior with the standalone Orchestrator v2023.10.1, which I suspect might be a bug.
I’ve initiated an Orchestrator HTTP request (POST) to activate an already existing trigger and reconfigure it with a specific Cron expression. Below is the payload for the trigger as an example:
“{Enabled: ‘true’,
Name: ‘12 IFRS16 Leasing - Balance Reports TEST’,
ReleaseId: 190,
ReleaseName: ‘12 IFRS16 Leasing - Dispatcher TEST’,
PackageName: ‘12_IFRS16_Leasing_Dispatcher’,
StartProcessCron: ‘0 0 13 18 3 ? 2024’,
StartProcessCronDetails: ‘{'type':5,'minutely':{},'hourly':{},'daily':{},'weekly':{'weekdays':},'monthly':{'weekdays':},'advancedCronExpression':'0 0 13 18 3 ? 2024'}’,
StopProcessDate: ‘2024-03-18T14:00:00Z’,
Id: 193}”
Initially, upon verifying the trigger’s status and configuration, everything appeares to be fine and functioning:
However, when attempting to edit the trigger, I encounter an error message stating “Invalid data received from server (#150)”, and the Cron expression remains unconfigured. Despite this, it’s worth noting that the trigger starts as expected and is properly configured for execution, but when editing it seems to not optain the cron expression from server.
See screenshot below:
What could be the cause of this error?