ExecuteCurrentActionAgainOnce
Hans Karlsen (talk | contribs) (Created page with "ExecuteCurrentActionAgainOnce is tightly coupled to rest calls to external services. see Documentation:OCLOperators_RestPost Its main usage is when a RestPost has failed, and you suspect that the reason for failure is a lapse of a accesstoken valid time. You would then want to silently use the refreshtoken to get a new accesstoken - and once you have the accesstoken you want to ExecuteCurrentActionAgainOnce") |
No edit summary |
||
| Line 1: | Line 1: | ||
ExecuteCurrentActionAgainOnce is tightly coupled to rest calls to external services. | ExecuteCurrentActionAgainOnce is tightly coupled to rest calls to external services. | ||
See [[Documentation:OCLOperators_RestPost]] | |||
Its main usage is when a RestPost has failed, and you suspect that the reason for failure is a lapse of | Its main usage is when a RestPost has failed, and you suspect that the reason for failure is a lapse of an accesstoken valid time. You would then want to silently use the refreshtoken to get a new accesstoken - and once you have the accesstoken you want to ExecuteCurrentActionAgainOnce. | ||
Latest revision as of 05:08, 2 May 2024
ExecuteCurrentActionAgainOnce is tightly coupled to rest calls to external services.
See Documentation:OCLOperators_RestPost
Its main usage is when a RestPost has failed, and you suspect that the reason for failure is a lapse of an accesstoken valid time. You would then want to silently use the refreshtoken to get a new accesstoken - and once you have the accesstoken you want to ExecuteCurrentActionAgainOnce.
This page was edited 15 days ago on 05/02/2024. What links here