Async Task Object Reference
On this page
Overview
StoreConnect queues each record refresh your store asks for as an Async Task and works through the queue in priority order, rather than refreshing every object at once. The records are readable so you can see where a refresh has got to. StoreConnect manages them: you do not create, edit, or delete them in normal use. Completed and failed tasks are deleted automatically seven days after they finish.
| Property | Value |
|---|---|
| API Name | s_c__Async_Task__c |
| Label | Async Task |
| Plural Label | Async Tasks |
| Type | Custom Object |
Fields
| Field Label | API Name | Type | Required | Description |
|---|---|---|---|---|
| Error Message | s_c__Error_Message__c |
LongTextArea(131072) | No | Why the task failed. |
| Job Type | s_c__Job_Type__c |
Picklist | No | Which processor handles this task. |
| Key | s_c__Key__c |
Text(255) | No | Identifies what the task is for within its job type, which is the object name for a refresh. A repeat request for the same object merges into the task already waiting for it. Once that task has started, a new request gets a task of its own. |
| Metadata | s_c__Metadata__c |
LongTextArea(131072) | No | Task progress, stored as JSON and rewritten as the task runs. To restart a stuck task from the beginning, clear this field and set Status back to New. |
| Payload | s_c__Payload__c |
LongTextArea(131072) | No | What your store asked for, stored as JSON. Do not edit it. |
| Priority | s_c__Priority__c |
Number(18,0) | No | Processing order within a job type. Lower numbers run first, and tasks sharing a number run together as a group. |
| Retry Count | s_c__Retry_Count__c |
Number(18,0) | No | How many consecutive passes have made no progress on this task. It resets as soon as the task moves. |
| Status | s_c__Status__c |
Picklist | No | Where the task is up to. New is waiting, Processing has a job running on it, and Completed and Failed are final. |
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.