Tweets not being sent on new CFP about cfpexchange HOT 7 CLOSED

Either that or the Azure Function fetch image call. I see that the latest added CFPs don't have their images hosted at our storage account. So might be that as well.

from cfpexchange.

Also why we need #81

from cfpexchange.

So this is why we're seeing the Error 500 pop up when submitting a CFP?

from cfpexchange.

Should be an asynchronous operation and not throw a 500 if background task doesn't work, but that's easily checked of course by turning off the feature toggle 😄

from cfpexchange.

I hate to break it to you @Jandev, but the error for this was due to the Azure Function or determining of the value of the feature toggle. I have implemented a try/catch around it and now it all works again...

from cfpexchange.

Figured as much when I saw you changing the appsettings from prefix.setting to prefix:setting.

Shame on me...

from cfpexchange.

But even now it doesn't seem to work for some reason. Have to get that app insights in there to see what is going wrong exactly. Anyway, this is done! 🙌

from cfpexchange.