When the handle-task route is called the task itself is executed succesfully.
But each "succesful" execution gives the following 500 error:
The principal (user or service account) lacks IAM permission "cloudtasks.tasks.delete"
Apparently gcloud wants to delete the task after completing it, when this fails this causes the task to be repeatedly called until the Max attempts limit is reached.
Adding the Cloud Tasks Task Deleter role to the Service Account resolved the issue for me.
But is this the expected behavior? If so this role should be added to the required roles in the readme.
When the
handle-taskroute is called the task itself is executed succesfully.But each "succesful" execution gives the following 500 error:
The principal (user or service account) lacks IAM permission "cloudtasks.tasks.delete"Apparently gcloud wants to delete the task after completing it, when this fails this causes the task to be repeatedly called until the
Max attemptslimit is reached.Adding the
Cloud Tasks Task Deleterrole to the Service Account resolved the issue for me.But is this the expected behavior? If so this role should be added to the required roles in the readme.