I doubt you can do much to improve the error reporting ("null" is apparently the error "message" returned by that specific provider, might be better with another provider).
IMO there are two possibilities depending on how many times you have: * ideally, fix that process to use a refresh token when one is provided by the provider * disable it by default (with a big warning in or check the release note expiration of the access token before trying to redo an update (and stop updating when it's outdated), maybe print a log
Thomas Mortagne on 21/Apr/26 12:25
I doubt you can do much to improve the error reporting ("null" is apparently the error "message" returned by that specific provider, might be better with another provider).
IMO there are two possibilities depending on how many times you have: * ideally, fix that process to use a refresh token when one is provided by the provider * or check the expiration of the access token before trying to redo an update (and stop updating when it's outdated), maybe print a warning log at this point
Thomas Mortagne on 21/Apr/26 12:26
I doubt you can do much to improve the error reporting ("null" is apparently the error "message" returned by that specific provider, might be better with another provider).
IMO there are two possibilities depending on how many times you have: * ideally, [optional but ideal I guess] fix that process to use a refresh token when one is provided by the provider * or check the expiration of the access token before trying to redo an update (and stop updating when it's outdated), maybe print a warning log at this point. That way we don't need to disable this feature by default.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
