-
mentax__what can cause a datastore_conflict error? What will be the best way to fix it?
-
mentax__"data": ⊖{
-
mentax__"message": "conflicting documents"
-
mentax__},
-
mentax__"error": "409",
-
mentax__"message": "datastore_conflict",
-
mc_mentax__: flush the db/doc from the cache and try the fetch/save again
-
mc_typically means two concurrent saves were attempted and one loses
-
mc_or the cache was stale (cached doc's _rev was older than the db's doc)
-
mc_409 just tells you to fetch from db again and apply your changes to the latest version of the doc
-
mentax__mc_: Thanks! Is there any sup command to do it?
-
mc_sup kz_datamgr flush_cache_doc {DB} {ID}
-
mc_i believe
-
BadRequestmentax__: sup kazoo_data_maintenance flush_docs {ACCOUNT_ID} {DOC_ID}
-
mc_BadRequest: flush_doc maybe ;)
-
mentax__sup kazoo_data_maintenance flush_docs 4192f51f74a0b48fb2e123a1d85388db
-
mentax__flushed all docs cached for account 4192f51f74a0b48fb2e123a1d85388db
-
mentax__it's working!
-
mc_good to start the day with a win
-
BadRequestmentax: calling that function with just the account_id is overkilling. You just clear all the other documents from that account from the cache. That is why there is a account_id -> doc_id variant ;)
-
mentax_BadRequest: I just didn't found which doc it is trying to touch
-
BadRequestI see.
-
SergeSo, with voip innovation they said that they can send messages over SIP. Does 4.3 support SMS over SIP?