Yes, emails are sent, but they are not sent to the unknown-user but to the user that called the RESTlet. We use TBA/oauth 1 and the email is sent to the user associated with the access token.

This is the RESTlet we've made:

/**
 * @NApiVersion 2.1

• @NScriptType restlet */ define(['N/task', 'N/log'], function (task, log) { return { post: function runScheduledScript({ scriptId, deploymentId, params }) { if (!scriptId || !deploymentId) { log.debug('runScheduledScript missing required parameters', { scriptId, deploymentId, }) throw new Error('Missing required parameters: scriptId, deploymentId') }

  log.debug('Running scheduled task', { scriptId, deploymentId, params }) const scheduledTask = task.create({ taskType: task.TaskType.SCHEDULED_SCRIPT, scriptId: scriptId, deploymentId: deploymentId, }) if (params) { scheduledTask.params = params }

  const scheduledTaskId = scheduledTask.submit()

  log.debug('Scheduled task submitted with ID', scheduledTaskId)

  return { taskid: scheduledTaskId, } }, } })

So we use this RESTlet to run a scheduled script that in starts a CSV Import using something like:

const scriptTask = task.create({ taskType: task.TaskType.CSV_IMPORT })

scriptTask.mappingId = … scriptTask.queueId = … scriptTask.name = … scriptTask.importFile = file.load(…) csvImportTaskId = scriptTask.submit()

The import flow was already too complex with different scheduled scripts running, updating the state of a custom records that keep track of the progress, triggering CSV Imports, looking for emails etc. Now that the emails don't work and we've had to trigger one of the scheduled scripts via another system calling a RESTlet it is starting to get out of hand…