[Question]: Update AL-Go System Files (403) Forbidden.`

[louagej]

Question

Hi,

I regenerated my GhTokenWorkflow because I added an extra repository in my organization. Since then, I have had problems running the action Update AL-Go System Files.

I've read a couple of issues that looked similar and tried steps I've used with different organizations and repositories, but none of these steps helped.

✅ Expiration Date of the GhTokenWorkflow is not > 6 months from now (Sept 12, 2025)
✅ GhTokenWorkflow has sufficient permissions
✅ GhTokenWorkflow's owner is the same organization the repo-actions are running in

Unfortunately, I kept getting this error: When I ran the action, I kept getting this error message: The remote server returned an error: (403) Forbidden.

Then I noticed the token only has visible fields Created on and Expires on. So, no visible field Regenerated on.

Then I thought, what if I just set back the Expires on to within six months of the Created on ... et voila 🚥

Is it possible that the period of validity of this token is interpreted from the Created on date of the token?

If this is the case, could it be an idea to put that on the Regenerated on (if that's available) date of the token?

[freddydk]

We just use the token as-is - and github determines whether it is valid.
Also, you don't have to regenerate the token after adding new repositories - they should automatically work.
You can attach the log or email it to me and I can see if I can see anything from the log.

[freddydk]

Tried ths same with this - works fine

[ChrisBlankDe]

I had the same issue.
my token was a bit older (mid 2024), but had no expiration date.
i have regenerated the token with an expiration date in 5 months.

after a new run it worked