Bad arguments to lookup in pairs

Discuss
#1

Continuing the discussion from Bad arguments to lookup in pairs:

the operation lookup in pairs cannot accept the arguments:, [datetime], [<!DOCTYPE], [not found] kodular
This comes out when I try to login in my app.
It has been working correctly for a long time all of a sudden started showing this even though I did not make any changes to the blocks.

Screenshot_20201223-222408
Screenshot_20201223-222408720×1600 154 KB

Below are my blocks

blocks
blocks839×544 19.3 KB

blocks (2)
blocks (2)2424×2660 588 KB

Please anyone who can help me…I will appreciate so much. Thanks

#2

There is simple answer
The api is not returning time in json text it is returning a !<Doctype so it is unable to find lookups in pair
I also get this error

#3

so please what might be the solution?

#4

You can do 2 things to stop the error

  1. Change your api to another good api that doesn’t return this error
    And 2. Is that hide the error with a condition like this
    blocks-1
    blocks-1786×160 17.2 KB

And do your rest code in then block

#5

thanks so much

#6

Did you read the api manual? It seems that something was missing …

#7

The issue is that it was working perfectly before. I made no change, all of a sudden it started this.

#8

It looks like your response content is coming with HTML. Review your blocks. …

#9

I used worldtimeapi.org
The response is in json

#10

At that moment, it seems not …

#11

I noticed something unusual now.
image
If i click the link of the api, it loads this.

#12

Do you think worldtimeapi expires over time?

#13

Your is ?

http://worldtimeapi.org/api/timezone/xxxx/yyyy ?

My is
http://worldtimeapi.org/api/timezone/America/Sao_Paulo

#14

http://www.worldtimeapi.org/timezone/Africa/Lagos

Africa lagos

#15

If i click your own local time. It loads the json, but when I click mine, it loads that previous screenshot I sent you.

#16

Your It’s work for me…

{“abbreviation”:“WAT”,“client_ip”:“16”,“datetime”:“2020-12-24T20:18:33.510452+01:00”,“day_of_week”:4,“day_of_year”:359,“dst”:false,“dst_from”:null,“dst_offset”:0,“dst_until”:null,“raw_offset”:3600,“timezone”:“Africa/Lagos”,"unixtime

1 Like
#17

Thanks so much for your assistance. I don’t know if this is related to my IP because other timezones load, but once I try loading that particular time, it gives me that.

#18

Did You check with my Location in your app ?

Did You check Response Content ?

#19

Let me do so

#20

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.