Timeline for Callout from Batch Apex not supported: Retrieving token
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 23, 2022 at 18:16 | history | suggested | Emmanuel BRUNO | CC BY-SA 4.0 |
Changed Scedule to Batch in title since it appears in comments that it's actually about batch, not scheduled
|
| Oct 23, 2022 at 14:33 | review | Suggested edits | |||
| S Oct 23, 2022 at 18:16 | |||||
| Sep 21, 2022 at 18:38 | comment | added | Arthur Almeida | I have one scheduler apex, one flow, and one apex to make integration, the scheduler calls the flow, and the flow calls the apex of integration, in this case, should give an error of "Callout from scheduled Apex not supported"? | |
| Dec 13, 2018 at 6:48 | history | edited | Reshma | CC BY-SA 4.0 |
Formatted code
|
| Dec 12, 2018 at 22:27 | vote | accept | j.koh | ||
| Dec 12, 2018 at 19:09 | history | edited | j.koh | CC BY-SA 4.0 |
added 256 characters in body
|
| Dec 12, 2018 at 16:26 | comment | added | Adrian Larson♦ |
Try moving your call to orderService.getAccessToken() inside your start method. You'll have to make it non-final.
|
|
| Dec 12, 2018 at 16:24 | history | edited | Adrian Larson♦ | CC BY-SA 4.0 |
added 16 characters in body
|
| Dec 12, 2018 at 15:41 | comment | added | j.koh | Sorry it is a batch apex | |
| Dec 12, 2018 at 15:41 | comment | added | Pranay Jaiswal | @j.koh You say Schedule APEX but I can only see Batch Apex in your code, can you confirm its Batch Apex you want and not Schduled Apex? | |
| Dec 12, 2018 at 15:32 | answer | added | David Reed | timeline score: 3 | |
| Dec 12, 2018 at 15:31 | history | edited | j.koh | CC BY-SA 4.0 |
added 267 characters in body
|
| Dec 12, 2018 at 15:25 | history | edited | Adrian Larson♦ | CC BY-SA 4.0 |
deleted 4 characters in body
|
| Dec 12, 2018 at 15:22 | history | edited | j.koh | CC BY-SA 4.0 |
added 243 characters in body
|
| Dec 12, 2018 at 15:20 | comment | added | j.koh | Yes I understand that, I'm trying to get this to work and then going in to clean up my code. | |
| Dec 12, 2018 at 15:18 | comment | added | Adrian Larson♦ |
You are abusing Test.isRunningTest() where you should instead use mocks. It won't fix your issue to resolve, but you should avoid this pattern at all costs.
|
|
| Dec 12, 2018 at 15:17 | history | asked | j.koh | CC BY-SA 4.0 |