404 Client Error on automated pipeline

Hello, we’ve been using twingate for a while and we wanted to run a script through an automated pipeline in github actions that runs every day at 4 am.
Whenever we run the pipeline manually, the run goes through perfectly, but when it runs automatically at 4 am, sometimes (about 50% of the time) the pipeline fails with a:
requests.exceptions.HTTPError: 404 Client Error: for url: https://placeholderurl.json

on twingate side, there doesnt seem to be anything weird on the connection logs, but itd seem like connection is breaking up randomly for the svc_account on the pipeline.

any ideas? Thanks!

Hi @nicolas.ferrovia,

since it breaks about 50% of the time, I wonder if there is a particular timeout at play somewhere? When there is an error, do you still see corresponding network events in the Admin Console for the right resource?

Connection is green on the admin console for the resource, everything seems to be in order, is there any sort of log or anything like that, that i could share that could provide more info?

Hi @nicolas.ferrovia,

you can click on the Resource that your github actions is connecting to via Twingate and should see all the activities there, I believe including activities generated by service accounts:

everything seems to be working fine here, even when the pipeline breaks, normally id assume twingate isnt the problem, but its a connection problem that only started after integrating twingate to the automation.

Hi @nicolas.ferrovia, is this endpoint a protected resource or is it a public endpoint used for populating fake data? Similar to what this page describes?

Typically 404 returns if the resource is not found and if this is a public endpoint, it might be that the resource isn’t available, invalid, or no longer exists.

Hey grady! This is the error i mentioned about the 50% success rate of the pipeline:

The resource itself isn’t public it is protected, i wrote “placeholderurl” simply not to write the name of our clients on the forum ticket!

The pipeline is running a cleanup service for Artifactory, we have Artifactory behind twingate so we need the agent to be able to send requests and delete packages thru the pipeline. It fails with the 404 error sometimes when trying to connect to one of these artifactory servers we have.

Hi Nicolas!

I think this one might require us to take a look at the logs for the headless client where the issue occurs. I have also noticed that you use the public API and are occasionally getting throttled (not that this would cause the issue above but perhaps we can help with that as well).

Would you mind getting the logs for the client and sending them to onboarding@twingate.com please?

Never mind that @nicolas.ferrovia, I just chatted with Grady, we will help via Slack.