# Add-on status still 'Processing'

**URL:** <https://community.servicem8.com/t/add-on-status-still-processing/833>\
**Category:** API & SDK\
**Created:** [September 12, 2019, 9:06pm UTC](https://community.servicem8.com/t/add-on-status-still-processing/833 "2019-09-12T21:06:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![developer](https://avatars.discourse-cdn.com/v4/letter/d/bcef8e/32.png) [@developer](https://community.servicem8.com/u/developer)\
**Post date:** [September 12, 2019, 9:06pm UTC](https://community.servicem8.com/t/add-on-status-still-processing/833/1 "2019-09-12T21:06:44Z")

</div>

**Originally posted by SL**

I updated my add-on w/ a new manifest.json file hours ago (this morning), but its status is still ‘Processing’, and when I try invoking my lambda function by clicking the add-on button, I see the error (in Cloudwatch logs) that  
{“errorCode”:403,  
“message”:“insufficient\_scope”,  
“additionalDetails”:“"read\_job\_contacts" scope required to complete this request”}  
But that scope is part of my updated manifest file, which shows that the add-on isn’t updated yet. Why’s it taking so long to process?