Hi @Hoang
This issue has been spotted for several Scope activities, as seen here:
Unfortunately, I don’t know the workaround for the Sharepoint activity package scope, but the underlying issue will soon be fixed with 2019.9.0 version.
In fact, you can try the beta version for a chance that the fix was already released