mirror of
https://github.com/ushahidi/SMSSync.git
synced 2026-04-25 15:55:57 +03:00
[GH-ISSUE #222] Result request interval in 2.7.1 #160
Labels
No labels
Bug report
Code improvement
Concern
Feature request
Feature request
Good first issue to work on
In progress
Needs info
Question
Ready
Translation
User Experience
User Experience
Website
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SMSSync#160
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @shtrih on GitHub (Nov 11, 2014).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/222
Are there any issues about separate requests with
?task=result? How often does SmsSync make this request? I set task check enabled with 1 minute frequency. Every minute I get requests to?task=sendbut none to taskresult. I got just one such request and don't know which event caused it.@eyedol commented on GitHub (Nov 12, 2014):
That is independent of the task frequency. It get triggered when an SMS is actually delivered by the device. Did you enable SMS delivery report?
@shtrih commented on GitHub (Nov 12, 2014):
Yes SMS delivery report is enabled. And SMS has been actually delivered but it stay in
Pendingwith statusFailed. Every minute (task check interval) SmsSync send this sms again. Displays toast messages one after the other:Copies of this message appears in
Sentlist. The taskresultnever be executed.@eyedol commented on GitHub (Nov 12, 2014):
How are you testing for the task result stuff on the server?
@shtrih commented on GitHub (Nov 12, 2014):
On server side in script I have following code (full code):
So I see all requests to the handler's URL in corresponding log file.
@eyedol commented on GitHub (Dec 1, 2014):
Fixed the broken result pull time frequency. This works with task checking frequencies.
@shtrih mind giving the latest develop code a test?
@eyedol commented on GitHub (Apr 16, 2015):
@shtrih no response. I'm assuming it's fixed. Feel free to re-open this if you experience this in latest stable release on the Playstore or the pre-releases.