REST oauth2 authentication in Scheduled/Triggered task

Summary (new/inexperienced user)
How do I configure a scheduled task/pipeline that hits a secured REST endpoint such that the oauth account required is authorized without manually intervention to allow use as a scheduled task?

Background
I have a pipeline that retrieves information from a REST end point.
This endpoint is secured using a Snap oauth2 REST account, which has been set up in the Account tab in the pipeline
This requires that “Authorize” button in the “Edit Account” window is clicked before the pipeline is executed.
This works fine and information is retrieved.

The pipeline needs to run as a triggered/scheduled task.
This fails unless the account used is pre-authorised manually before the task is run, which is not practical.

What am I missing?

How do I configure the scheduled task/pipeline such that the oauth account is authorized without manually intervention to allow use as a scheduled task?

@andrew_wait

I don’t know if this will helps, but on the REST OAuth2 there is an option/checkbox called “Auto - refresh token”, with which the token will be automatically refreshed, once expired.

If that not works, then probably the best is to create a ticket to the Support team.

Regards,
Spiro Taleski