To start or stop a task based on an ID, you can use the eight-character object ID for the task or the federated task ID.

To find the eight-character object ID, see Tasks. However, this resource returns a task ID that you can use only to run tasks located in the Default folder.

If your organization uses projects and folders, see Lookup or Objects to retrieve the federated task ID.

For a

Data Ingestion and Replication

file ingestion and replication

task, use the

file ingestion and replication

job resource. For more information, see File Ingestion and Replication REST API.

When you include the callbackURL in the job request, the service sends a request to the callback URL when the job completes. The service always uses a JSON request for callbacks.

A callback might be called multiple times. For example, multiple callbacks might occur in the following situations:

Your callback server returns an HTTP status code other than 200.
Your callback server doesn't respond within 30 seconds.
Your callback server is down.
There is a transient network failure.

In any of these situations, the URL connection breaks and the service counts the break as a failed attempt. The service will make three immediate attempts to receive a successful response. Afterward, the attempts will occur in exponential increments. For example, the attempts might begin with a 30-second interval and progress up to a maximum 3-minute interval, until the total time reaches 30 minutes.

The service runs the POST request from the callback URL. The following text is a sample response:

 {
    @type:"callbackUrlResponse"
    endTime: "2013-02-27T18:57:52.000Z",
    objectId: "0034J90000000M",
    objectName: "taskName",
    runId: 5,
    status: "COMPLETED" // or “FAILED”
}