We're updating the issue view to help you get more done. 

An error occurs if using an ad-hoc task and no site context for tasks has been specified

Description

If I use an ad-hoc task it results in a 500 error on completion if no site context has been specified.

The site context needs to be specified in the scheduled task configuration.

It would be good if it would automatically fall back to the default site. or if the context is automatically set to default. The error is otherwise tough to debug.

Environment

None

Status

Assignee

Unassigned

Reporter

Jan Jannek

Labels

None

Accepted

Yes

Fix versions

Affects versions

10.9.0

Priority

Low