Skip to content

Troubleshooting

Everything can't be 🌈 and 🦄, sometimes there is an issue to troubleshoot.

Logs

It is strongly recommended to enable logging at INFO level for the task handler and task scheduler services as there are plenty of useful logging done by the task in this package. Looking at WARN and ERROR will tell you when something goes wrong but INFO will also tell you when schedules are skipped "by design".

Universal checklist

If you expect lime objects to be created but they aren't, ask yourself these:

Is the task scheduler running?

The task scheduler must be running for this package to work. Check the status of the windows service if on-prem and the kibana logs if in cloud.

Is the task handler running?

The task handler must be running for this package to work. Check the status of the windows service if on-prem and the kibana logs if in cloud.

Do the logs say anything?

The scheduled task runs every hour so the logs for the task handler should have log messages on the INFO level every hour. If there is a WARN or ERROR associated with the schedule it should be easy to proceed and fix it.

If you see logs for the task scheduler but nothing for run_lime_objects perhaps the task@scheduledlimeobject doesn't exist?

Is there at least one affected object / parameterset for the schedule?

It is not possible to generate limeobjects from schedules unless there are parametersets on them.

Is the schedule active?

Each schedule has an Active property (yesno) that controls if it should be processed or not. It most likely defaults to no. This is to prevent the schedule from running before the user is done configuring it.

Does the schedule editor look ok?

Open the Schedule Editor in the web client and make sure the schedule looks reasonable.

If there is a problem with the Schedule Editor open the developer tools in the browser (F12) and refresh the page. The have a look any errors are written to the console or any of the web requests are failing when attemping to open the Schedule Editor again.

Is the schedule previewed in the editor?

The Schedule Editor contains a preview of dates at which to create limeobjects for. If it can't be previewed there is something wrong with either the schedule configuration or the runtime configuration.

What if you try running it again (as your user)?

The Run schedule now button in the webclient immediately triggers the schedule and will run the task as the currently logged in user. If it only works when running like this it is most likely a permission issue for the scheduled task's user.

Should the schedule even create any limeobject?

Limeobjects will only be generated when its time do so, consider the target date it is not creating limeobjects for and try these rules:

  • Target date > lastcreated, otherwise it has already been processed
  • Target date >= startdate, otherwise the schedule has has not started yet
  • Target date <= until, otherwise the schedule has ended
  • Target date - createdays <= NOW(), otherwise its not time to do it yet
  • Target date is less than 5 years into the past (500 days for DAILY)
  • Target date is less than 5 years into the future (500 days for DAILY)
  • The upper limit count has not been reached yet, otherwise the schedule has already run the maximum allowed times
Back to top