Had a build that in my "builds" list was stuck in a "building" state. Now causing issues in umbraco publish

Build was stuck in “building” state. When clicking on the build it was showing as a build which had gone through but on the list of all my builds it was stated as “building”. I went on to “delete deploy”, but afterwards it caused issues with our build trigger in umbraco. So we can no longer trigger builds from an umbraco publish, which we could previously.

project name: ffefonden-prod

Can no longer see the build and state it, in this message as i deleted it:

Looks like the deploys are working? I’m not seeing any stuck or failed builds in your account not, so I’m unsure what you mean by “no longer trigger builds”. What error are you getting?

It was a deploy which was there, but i deleted it, so it’s no longer visible.
Im not sure if our issue is directly related to this. But when trying to run builds from our netlfiy client in umbraco. We get 404 from the api now.

ex: https://api.netlify.com/api/v1/sites/{siteId}/builds
We have checked the siteId, and we are 99% it’s the correct one from netlify.
Its all our projects in that team which are returning 404.

Have you checked your API token?

Thanks for your response, made me realise it’s most likely the access token which is causing issues. We recently removed a former employee from the team, and it might have been his access token it was connected with.
If i need to setup a new access token, im guessing i need to make a personal one for my account then. Do you know if i need to use OAuth or “personal access token”?

Personal Access Token