It doesn't run on schedule at all

[soonictm]

Unless I'm missing something, it runs once in a Window and sits there forever - never refreshes on it's own anymore.

I'm using Windows, Feeder, latest version 1.1.0.

[soonictm]

I dont even think it does anything on that first run either. Checked my properties files and nothing gets added.

[ColeBennett]

What interval do you have?

[soonictm]

5 minutes. But I noticed it does not edit my SOM pairs at all.

On Thu, Feb 15, 2018 at 10:34 PM, Cole notifications@github.com wrote:

What interval do you have?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bennettca/binance-auto-blacklist/issues/16#issuecomment-366084517, or mute the thread https://github.com/notifications/unsubscribe-auth/AbfOjv42PRaMpwJi5GLPCuodEI_mz9ITks5tVLDjgaJpZM4SE6O- .

[ColeBennett]

Should only edit SOM pairs if a new coin is listed though, did it say a new pair was released in the console?

[soonictm]

Output below. Cant see anything like that, but i know that it didnt catch RPX 2 days ago and I was trading this brand new coin:

2018-02-14 12:06:54 INFO Loaded settings 2018-02-14 12:06:54 INFO enabled = true 2018-02-14 12:06:54 INFO interval = 5 minutes 2018-02-14 12:06:54 INFO market = BTC 2018-02-14 12:06:54 INFO days = 14 2018-02-14 12:06:54 INFO clear = true 2018-02-14 12:06:54 INFO Set to query https://support.binance.com/hc/en-us/sections/115000106672-New-Listings every 5 mi nutes 2018-02-14 12:06:54 INFO Fetching data... 2018-02-14 12:06:56 INFO - RPX parsing https://support.binance.com/hc/en-us/articles/360000842472-Binance-Lists-Red-Pu lse-RPX- 2018-02-14 12:06:56 INFO - AE parsing https://support.binance.com/hc/en-us/articles/360000668312-Binance-Lists-Aeterni ty-AE- 2018-02-14 12:06:57 INFO - BLZ parsing https://support.binance.com/hc/en-us/articles/360000638211-Binance-Lists-Bluzel le-BLZ- 2018-02-14 12:06:57 INFO - VIA parsing https://support.binance.com/hc/en-us/articles/360000564532-Binance-Lists-Viacoi n-VIA- 2018-02-14 12:06:57 INFO - NANO parsing https://support.binance.com/hc/en-us/articles/360000532912-Binance-Lists-Nano- NANO- 2018-02-14 12:06:58 INFO - STEEM parsing https://support.binance.com/hc/en-us/articles/360000492012-Binance-Lists-Stee m-STEEM- 2018-02-14 12:07:00 INFO - CHAT parsing https://support.binance.com/hc/en-us/articles/360000447931-Binance-Lists-ChatC oin-CHAT- 2018-02-14 12:07:01 INFO - IOST parsing https://support.binance.com/hc/en-us/articles/360000235812-Binance-Lists-IOSto ken-IOST- 2018-02-14 12:07:02 INFO - PIVX parsing https://support.binance.com/hc/en-us/articles/360000216591-Binance-Lists-PIVX- PIVX- 2018-02-14 12:07:03 INFO - INS parsing https://support.binance.com/hc/en-us/articles/360000008412-Binance-Lists-INS-Ec osystem-INS- 2018-02-14 12:07:03 INFO - RLC parsing https://support.binance.com/hc/en-us/articles/115003950952-Binance-Lists-iExec- RLC-RLC- 2018-02-14 12:07:04 INFO - VIBE parsing https://support.binance.com/hc/en-us/articles/115003879851-Binance-Lists-VIBE- VIBE- 2018-02-14 12:07:05 INFO - APPC parsing https://support.binance.com/hc/en-us/articles/115003793551-Binance-Lists-AppCo ins-APPC- 2018-02-14 12:07:07 INFO - TRIG parsing https://support.binance.com/hc/en-us/articles/115003697872-Binance-Lists-Trigg ers-TRIG- 2018-02-14 12:07:08 INFO - LUN parsing https://support.binance.com/hc/en-us/articles/115003672371-Binance-Lists-Lunyr- LUN- 2018-02-14 12:07:09 INFO - NAV parsing https://support.binance.com/hc/en-us/articles/115003668252-Binance-Lists-NAV-Co in-NAV- 2018-02-14 12:07:10 INFO - WINGS parsing https://support.binance.com/hc/en-us/articles/115003643971-Binance-Lists-Wing s-WINGS- 2018-02-14 12:07:11 INFO - EDO parsing https://support.binance.com/hc/en-us/articles/115003647752-Binance-Lists-Eidoo- EDO- 2018-02-14 12:07:12 INFO - NEBL parsing https://support.binance.com/hc/en-us/articles/115003598012-Binance-Lists-Nebli o-NEBL- 2018-02-14 12:07:13 INFO - AION parsing https://support.binance.com/hc/en-us/articles/115003580272-Binance-Lists-Aion- AION- 2018-02-14 12:07:15 INFO - ELF parsing https://support.binance.com/hc/en-us/articles/115003576472-Binance-Lists-%C3%A6 lf-ELF- 2018-02-14 12:07:16 INFO - OST parsing https://support.binance.com/hc/en-us/articles/115003530072-Binance-Lists-Simple -Token-OST- 2018-02-14 12:07:17 INFO - ICX parsing https://support.binance.com/hc/en-us/articles/115003507132-Binance-Lists-ICON-I CX- 2018-02-14 12:07:18 INFO - WAVES parsing https://support.binance.com/hc/en-us/articles/115003455711-Binance-Lists-Wave s-WAVES- 2018-02-14 12:07:19 INFO - TNB parsing https://support.binance.com/hc/en-us/articles/115003451291-Binance-Lists-Time-N ew-Bank-TNB- 2018-02-14 12:07:19 INFO Loaded 25 newest listings (Took 24438 ms)

On Thu, Feb 15, 2018 at 11:00 PM, Cole notifications@github.com wrote:

Should only edit SOM pairs if a new coin is listed though, did it say a new pair was released in the console?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bennettca/binance-auto-blacklist/issues/16#issuecomment-366090961, or mute the thread https://github.com/notifications/unsubscribe-auth/AbfOjitcPpXTRPZC5Ch3kZNzLisRSbZsks5tVLcLgaJpZM4SE6O- .

[clownfish44]

Issue is that your appsettings.json is not correct format please validate it here https://jsonlint.com/ and it will work fine

[soonictm]

Ah right, you mean comments there with // chars. Shame, its useful to have comments in json file. Is there a way to have them in compatible way (json)?

On Fri, Feb 16, 2018 at 2:04 PM, clownfish44 notifications@github.com wrote:

Issue is that your appsettings.json is not correct format please validate it here https://jsonlint.com/ and it will work fine

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bennettca/binance-auto-blacklist/issues/16#issuecomment-366243672, or mute the thread https://github.com/notifications/unsubscribe-auth/AbfOjpc8OmzWsY8S7dy4iVUUjsPt2UaDks5tVYsHgaJpZM4SE6O- .