Issue in Integration of Facebook with GAD

[JJay]

Hi,

Im working on Genesys integration with social media (facebook and twitter).
All the configuration and applications are installed as per the document.

Im facing the following problem
[color=red][b]  Comment given by the user from facebook is coming twice on GAD window.[/b][/color]


1.The user logins to facebook and gives comment on XXX [b]facebook page wall [/b] whose access token is configured in genesys sms server.
2.Posted comment on the XXX facebook page wall comes as a interaction on GAD.
3.Agent accepts the interaction, and replies to the comment, clicks "Done" and close the interaction.
4.After closing("Done") that interaction , same interaction is coming again on GAD.

Please let me why the same interaction is coming twice on gad.
If i have missed anything else.

Thanks
Jaykumar.

[René]

Hi Jaykumar,

It is very hard to help you without seeing logs. However, I would recommend you to review interaction flow used for routing of facebook interactions created by agent (=replies).

R.

[JJay]

Hi Rene,

Thanks for replying. Two interaction issue got resolved . It was Social Messaging Server configuration issue.

However, Social Messaging Server unable to get updates from Facebook. fql.multiquery fails to execute.

We are getting the following error in Social messaging Server logs:
17:05:49.072 Std 42400 error... (channel-facebook).(monitor).(event) exception while reading updates {[color=blue][b]message:Received Facebook error response (code 602): canvas_name is not a member of the application table[/b][/color].}
com.restfb.FacebookResponseStatusException: Received Facebook error response (code 602): canvas_name is not a member of the application table.
at com.restfb.BaseFacebookClient.throwLegacyFacebookResponseStatusExceptionIfNecessary(BaseFacebookClient.java:110)
at com.restfb.DefaultFacebookClient.throwFacebookResponseStatusExceptionIfNecessary(DefaultFacebookClient.java:495)
at com.restfb.DefaultFacebookClient.makeRequest(DefaultFacebookClient.java:453)
at com.restfb.DefaultFacebookClient.executeMultiquery(DefaultFacebookClient.java:298)
at com.genesyslab.mcr.facebook.monitor.MonitorBase.getStreams(MonitorBase.java:1020)
at com.genesyslab.mcr.facebook.monitor.MonitorBase.ProcessFqlAndSubmitItx(MonitorBase.java:891)
at com.genesyslab.mcr.facebook.monitor.MonitorBase.ProcessFqlAndSubmitItx(MonitorBase.java:868)
at com.genesyslab.mcr.facebook.monitor.FacebookMonitor.readInteractions(FacebookMonitor.java:39)
at com.genesyslab.mcr.facebook.monitor.MonitorBase.run(MonitorBase.java:140)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

Thanks.
Regards.
JayaKumar

[aj]

This is due to a recent change in the FB API. A hot fix should be available shortly (if not already).