Adding action w/status = asap creates action but status is queued

sloftin at February 16th, 2018 09:24 — #1

Hi. I am seeing the incorrect status being set when I create an action on an existing contact. I send 'asap', but the status always gets set to 'queued'. Would appreciate some help resolve this. Here is a sample call/response.

Thanks,
Scott

CRM API call:full (POST) url is [https://app.onepagecrm.com/api/v3/contacts/5a86d115e1c1a830163169a4/actions.json]
Array
(
[contact_id] => 5a86d115e1c1a830163169a4
[date] => 2018-02-16
[text] => Setup Leads for Scott (ASAP)
[status] => asap
)
CRM Response:stdClass Object
(
[status] => 0
[message] => Created
[timestamp] => 1518788834
[data] => stdClass Object
(
[action] => stdClass Object
(
[id] => 5a86e0e2e1c1a87784312567
[assignee_id] => 55db59ef1787fa41ca00030e
[contact_id] => 5a86d115e1c1a830163169a4
[text] => Setup Leads for Scott (ASAP)
[status] => queued
[done] =>
[created_at] => 2018-02-16T13:47:14Z
[modified_at] => 2018-02-16T13:47:14Z
[position] => -1
)

)

pawelsmolinski at February 16th, 2018 09:41 — #2

Hey Scott, could you could you check if this specific contact has already some action assigned to given user? If yes, then every new action created for the same contact and assignee will be marked as queued as single user can have only one non-queued action for specific contact.

vladimir at February 16th, 2018 11:08 — #3

Hi Scott!

All ASAP actions are queued. Once a user has resolved an ASAP action, the next ASAP action is shown to the user.

Thank you,
Vladimir Konnov