Infinite Recursion Protection Help

I do my own OAuth token and twitter token expires after 2 hours. So of course the refresh workflow stops after 11 depth.

My question is, is there a way for a workflow to ignore Infinite Recursion Protection? I read the docs and it seems like the only way is to just increase the limit.


My current solution is to have a 5,000 limit. Base on the math for one users twitter needs around 4.5k depth to refresh the user token for a year.

Hey @sheepherd.co,

You can actually set it to “No limit” under Settings > API

Ya i saw that. Bubble suggest not to do that just in case. So I just did the math on how many times a year the twitter refresh flow would have to be used and I used that as the limit.

You can use it with no limit, just be careful.