API response disappears after 0.1 sec..

  • /attachments/1326966879885197374/1326966880803618827/Screen_Recording_2025-01-09_at_19.29.32.mov

    unicodes

    5 days ago

    I'm getting the response for 0.1 seconds then disappears.
    Why the response disappears? It does it on PATCH.
    Screenshot_2025-01-09_at_19.30.20.png
  • Lee Russel

    4 days ago

    @unicodes What is the settings of your API? Is auto fetch on?
  • Lee Russel

    4 days ago

    Can you also screenshot what the input value to your api looks like from the perspective of your backend
  • Andreas Møller

    4 days ago

    Any chance that the API is depending on some data that is updated when the request is done?
  • /attachments/1326966879885197374/1327596360299577355/Screenshot_2025-01-11_at_13.13.01.png

    unicodes

    4 days ago

    Hi @Lee Russel , the API is the default one, there are no extra settings. There are no input values, just the id of the object updated and the id exist as the update is performing but no response in the API.
    Screenshot_2025-01-11_at_13.13.01.png
  • @Andreas Møller There are no dependencies from other APIs, it is just a PATCH with id and simple body to a variable.
  • Screenshot_2025-01-11_at_13.15.11.png
  • Screenshot_2025-01-11_at_13.15.42.png
  • Screenshot_2025-01-11_at_13.15.58.png
  • Andreas Møller

    3 days ago

    Ah I think I know what is happening. When the api is checked it see if it should update it sees that the body is different since the timestamp has changed
  • unicodes

    3 days ago

    Do you know please If I can do something to fix this or is from toddle team to be fixed?
  • Andreas Møller

    3 days ago

    Unfortunately this might take some time for us to fix, so I would recommend not using autofetch for now
  • unicodes

    3 days ago

    It is a PATCH, i'm calling it just on button click not auto fetch. Do you want me to open a bug on this or will you communicate with the team?
  • Screenshot_2025-01-11_at_14.07.08.png
  • Andreas Møller

    3 days ago

    Yes please do.
  • Lucas G

    3 days ago

    Yeah this happens when using formulas that constantly update like that directly in the body as Andreas said.
    @Andreas Møller once I left auto-fetch on and sent like 5k+ requests before I unchecked auto-fetch 😬
    🙏1
  • Good times
  • I didn't really think of it as a bug though
    ❤️1
  • unicodes

    3 days ago

    Thank you Lucas! I'm not using auto-fetch, I do not know why is happening this issue without auto-fetch.
  • Lucas G

    3 days ago

    Because of your now node
    😅1
  • It might be a bug or not depending on how you look at it
  • unicodes

    3 days ago

    I have to check this without now 😅
  • Lucas G

    3 days ago

    If you set the payload to a variable it should go through (even with the now)
  • It's what Andreas said, it's because the body is changing
  • Definitely do not leave auto-fetch on or you'll stress test whatever is receiving this call lol
  • unicodes

    3 days ago

    I do not know if it was fixed, but with now and without now works. ❤️
  • No, it don't
  • unicodes

    3 days ago

    You are right Lucas, without now works fine
  • Thank you! It is a solution in case the toddle team would consider to fix or not depending of how they consider this (a bug or not).
  • But I'm happy to find the issue! Thank you!
  • Andreas Møller

    3 days ago

    It sounds like it is. We will look into it on Monday
    🙏1
  • unicodes

    3 days ago

    Thank you Andreas and Lucas for your support!
  • Lucas G

    3 days ago

    On a side note. In supabase you can set up a function that automatically updates the “updated” column any time it is changed
    🥰1
  • There is a quick plugin/function for it
  • Or you can set it up in sql editor
  • unicodes

    3 days ago

    Wow, great ideea! Thank you!

Stop scrolling. Start building.

toddle is a visual web app builder that rivals custom code — but accessible to your entire team!

Try toddle — it's free!

© Copyright 2024 toddle. All rights reserved.